I'm still getting my feet wet with Arch and so far have only used ABS to make a few packages that I haven't found in the repos.I didn't realize how much was involved with those apps. For right now, I think I'll have to keep it simple so I don't overdose.
]]>In makeworld, I would have it ask the user which tree to build and list all the common options (c,f,i,b) with a default to makeworld -c. After the build it would be nice to compare the folders with the built and verify a successful build of the entire tree (obviously it couldn't always work with the -b option if there are more subdirectories within the current that brings some 'orphan' packages not native to the tree)
Gensync maybe a pain. I would have it ask the user where to create a directory for each tree that would store the package, which then would make the dir and the <dir>db.tar.gz. in it. Have it ask the user for which tree to compare the md5sums to the destined directory with the packages in it. Sync /etc/pacman.conf with the new location for the newly created directory. Refresh pacman with pacman -Sy.
To gensync all packages in /var/abs everything would be the same but it should back-up the existing /var/cache/pacman/pkg (because they are arch packages with different md5sums) and create a new. I would also have it comment out the arch mirrors in /etc/pacman.conf(to not conflict with existing packages). This all would have to be done before a pacman refresh......This entire package rebuild option probably would not be worth doing, as most people probably would not rely exclusively on building their own packages instead of using the arch repo. Entire trees would have to be done at a time and it would eat up tons of hd space. But with all the space I have, I for one would
Like I said, you would really have to read the man pages to understand what the hell I was talking about. And the actual design its self would probably be easier for you to do. Im just offering some basic structure ideas.
]]>I would find your program very usefull if it incorporated these utilities in it. I would even offer to help, but I haven't learned java yet.:cry:
Well, if you're wanting to help, I can write the code fairly easily. The hard part for me is designing a clean interface for all those options. If you are interested in modifying my screenshots to show a good layout for components, I'm in.
]]>what about other options for makepkg? Like -ci to clean workfiles and install the package after the build. genysnc, makeworld, etc. Just a thought..
pacman -U upgrades/installs the package. I've only used ABS sparingly, so I've never delt with the -c function. There's obviously a lot more that can be done with it - maybe a text field for additional switches on makepkg/pacman? and a text area for additional free-form commands?
]]>It would be really be nice to have a script or program to automatically execute after an abs update that would allow you to choose to build packages if desired. I haven't really given much thought into it though....
]]>Java app, I'm happy!!!
]]>http://sudstyle.freecoolsite.com/screenshots.html
EDIT: Broken links to screenshots fixed!
]]>I would welcome the community's opinion of my implementation and presentation of the application. The JAR File can be found at http://sudstyle.freecoolsite.com/ssabsgui.jar and can be run with:
java -jar ssabsgui.jar