On Thu, Dec 4, 2008 at 8:53 PM, Allan McRae <allan@archlinux.org> wrote:
Aaron Griffin wrote:
On Thu, Dec 4, 2008 at 1:14 PM, Allan McRae <allan@archlinux.org> wrote:
Hi,
I have written a couple of script that other here might find useful.
...
The rebuildorder script is my first "real" python script so it could probably be improved. If people think that these would be useful to have somewhere, I can tidy them up a put them in a git repo somewhere.
I'd say stick them in the devtools repo. This looks to be a little better than the 'lddd' script in there already. Would you mind doing a once-over to see if lddd does anything this script does not?
This rebuildlist script has a different goal than lddd. It looks for packages that will need a rebuild for a given library soname bump. Lddd checks for packages that are linked to any missing libraries. So one is a library specific pre-rebuild tool and one is a more general system checking tool. I'm looking at how I can improve the rebuildlist script, as even though it is more specific that lddd it takes longer to run. I think that this is because lddd restricts the directories for the files it test. I'm looking for a way to do that without getting (too many) false negatives. It also only scans packages on your computer so will miss (many) needed rebuilds. Idea welcome.
Perhaps make it so it can be run on gerolde? That way we can access all packages in the repos