On Thu, Apr 09, 2009 at 11:32:22AM +0200, Alan McKinnon wrote: > > > is there a good reason to remove them, instead of masking? > > > > If you like spending half a day masking hundreds and hundreds of > > packages using an inflated package.mask, then no, there's no good reason :) > > The OP said "a couple of packages", so package.mask is the best bet.
Give OP the benefit of doubt that he might know what he is asking and why. > PORTAGE_RSYNC_EXTRA_OPTS is probably not the best way - if one of those > packages is in a DEPEND that is needed somewhere, portage will throw a hissy > fit about missing stuff. If masked, at least you get a parseable error message # mv /usr/portage/dev-libs/apr /tmp/ # emerge -va apache These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy "=dev-libs/apr-1*". (dependency required by "www-servers/apache-2.2.10" [ebuild]) (dependency required by "apache" [argument]) Does look like an informative message to me rather than a hissy fit. -- Eray
