On Thursday 13 November 2003 01:42, rd wrote: > Thanks for clearing up my confusion regarding the > /etc/portage/package.(mask,unmask) function. I use it to > mask out apache2, but did not understand the fact that it > was limited to the contents of /usr/portage/package...
No, that sounds like you're doing the right thing. In this case you have added a package to /etc/portage/package.mask, right? You could copy the ebuild to your overlay and mask it with -arch but then it would no longer be applicable when a new version comes out. If you don't ever want a package installed and want to prevent other packages from installing it then /etc/portage/ package.mask is the way to go. /usr/portage/package.unmask is the one that confuses most people because they don't understand the different ways a package can be masked. To reiterate, portage.unmask only unmasks packages which have been masked via /usr/portage/ profiles/package.mask; it has no affect on ~arch or -arch. Jason -- [EMAIL PROTECTED] mailing list
