On Saturday 13 January 2007 06:09, Willie Wong wrote: > Oh, that is too bad.
Unless you have a lot of overlays it not really *that* bad. [SNIP] > Just a thought though: would the following be advisable/work? > > Could I just delete those relevant overlays (either layman -d or > perhaps commenting them out in the relevant parts of the make.confs) > and see if emerge complains about non-existant packages in my world > file or unsatisfiable dependency? IIRC, I shouldn't have any packages > installed from overlays for more recent versions than portage offered; > I only install them from overlays when the ebuilds are not in portage > at all. # PORTDIR_OVERLAY="" emerge -ep world >/dev/null !!! Ebuilds for the following packages are either all !!! masked or don't exist: dev-util/regex-coach app-portage/pfs net-analyzer/ksniffer kde-misc/kcpufreq app-portage/gentoo-stats So yeah, that works. :) IMO the real solution for your problem, however, is a package manager with true multiple repository support allowing you to control from which repository you want to install a given package. I'm not sure if pkgcore is there yet (since I don't follow it too closely), but paludis is. Paludis thus also stores information about which repository a package was installed from. With portage if the same ebuild or eclass exists in any of your overlays and in the tree then the one in the tree will just be hidden to portage behind the overlay. That's why they are called overlays in the first place.. ;) -- Bo Andresen
pgpbMtpxNBKso.pgp
Description: PGP signature
