On 06/26/11 15:44, Benedikt Böhm wrote: > On Sun, Jun 26, 2011 at 4:59 AM, Stuart Longland <redhat...@gentoo.org> wrote: >> - revdep-rebuild (handles packages broken by soname changes, etc) > > solved by preserved-libs in portage-2.2
Hmmm, except that portage-2.2 isn't stable yet... indeed it isn't even out of alpha yet. Not going to unleash that on my production systems. The reason why some of these things get out of date to this extent is because I'm in the "it ain't broke, don't fix it" camp much of the time, and so outside the kernel and a few other applications, I just keep things plodding along as they are. I then get bitten a little when I go to update. Unstable portage is kinda an iffy area when dealing with production machines... experimental boxes, no worries... but not on machines I depend on for work. >> - python-updater (handles Python module rebuilds after upgrading Python) >> - perl-cleaner (handles Perl module rebuilds after upgrading Perl) > > these just exist because python and perl ebuilds are horribly broken. > take a look at RUBY_TARGETS or PHP_TARGETS for an example of how to do > it right. this would also fix all the failures that python and perl > introduce to binary packages. Perhaps there is room for improving things there... that's a more long-term solution however. This will require some careful forethought. Modifying the above tools though, to spit out a list of packages, shouldn't be much of a change... and then making a tool that can collate this information and merge it (revdep-rebuild has this code already) shouldn't be that much of a burden to maintain in the short term. -- Stuart Longland (aka Redhatter, VK4MSL) .'''. Gentoo Linux/MIPS Cobalt and Docs Developer '.'` : . . . . . . . . . . . . . . . . . . . . . . .'.' http://dev.gentoo.org/~redhatter :.' I haven't lost my mind... ...it's backed up on a tape somewhere.
