Duncan wrote:
I don't have a particular dog in this fight, but that's not the same thing. --skip-first allows the admin to react to whatever when wrong, try to fix it, and use the skip option only if he decides it's warranted. IOW, it's sort of interactive, tho over time. It appears this option must be added at the beginning, before one knows there'll be an error, and independent of what that error might be. (I'm assuming paludis creates a log of what failed, so one can try them again later, after fixing the problem or getting a package update or whatever.
Sure it does - but you can go one better. When paludis dies it can be asked to create a resume script - a command line that will resume where it left off. This will include all the packages that it hadn't yet installed. You can edit this command line as you please and execute it.
It isn't exactly --skipfirst, but it is better in some regards and maybe worse in others.
Oh, even if you don't want to use paludis as your package manager you might want to look at adjutrix. There are scripts that do the same sorts of things with portage, but adjutrix can do reverse deps in seconds, or a comparison of amd64 to x86 for keywording purposes.
Also - paludis's support for GLSAs is nice - paludis -i security will install all security updates, and paludis --report will catch any unfixed GLSAs.
Again - the best package manager is situation-dependent. I'm occasionally disappointed by some of paludis's developers (and some of its detractors), but it is a very capable piece of software.
-- [email protected] mailing list
