Beso <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Tue, 14 Aug 2007 00:35:13 +0200:
> paludis is not a replacement. i've never said that is a replacement. i > only suggested it for a report of the system. it's safe to have > installed 2 package managers and you could also use them both > independently. when you use paludis to update the package db of your > world, the first time you'll use portage it will reread the package db. > the same goes for paludis: when installing something with portage you'll > have to regenerate the installed cache. > trying it out for the report only with --report option (it doesn't > modify effectively your world packages) is safe. it only sows out > incoherences in world db, and then you can use portage to remove/modify > the packages that paludis signals as not ok. FWIW, I've never used any fully independent package manager and likely won't for awhile (for me, portage is decently fast on a dual-core or dual- cpu, at least after the initial emerge --pretend world to bring all those files it reads into cache, and assuming one has sufficient memory as I do to keep it there), but the same idea of effectively getting a "second opinion" applies to a tool I use, "dep", from the udept package. dep doesn't always get all the dependencies exactly right, so I don't trust it to actually change anything, but I've found it EXTREMELY useful as that "second opinion" on occasion. It has some VERY useful modes of operation, like telling you what entries in your world file it thinks can be removed, as they are a dependency of something else in the world file. As I said, I don't fully trust it, so I always use --pretend and use it to get a list, then act on the list myself, rather than letting it do it. However, just getting that list is the useful thing, and VERY useful it is! The other dep function I find useful, and actually use even more, is the - j (view changelog) option. Do you ever wonder why portage is telling you it wants to downgrade something, and get frustrated because portage won't output anything for its --changelog (-l) function unless it's an upgrade? What about those times when the dev made a minor screwup in the changelog entry format, so portage can't parse it and refuses to output anything for --changelog? dep -j <package> to the rescue! So anyway, you may wish to try emerging udept, as it's a quite handy utility to have around, for its second opinions and otherwise, or at least I've found it so. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [EMAIL PROTECTED] mailing list
