On Sun, 3 Apr 2022 at 11:54, n952162 <n952...@web.de> wrote: > I'm not really clear on masking. > > 1. My /etc/portage/package.accept_keywords has no mention of glibc, so I think there's nothing to unmask.
This file is for adding or removing keywords from packages (like amd64 or ~amd64). To "unmask and enable the crypt USE flag of sys-libs/glibc" you would put this in /etc/portage/package.use.mask: sys-libs/glibc -crypt > 2. "mask the system USE flag"? USE flags go into /etc/portage/package.use, correct? Is that "mask" an inexact expression? Anyway, a "system" USE flag? This file is for setting or unsetting USE flags on a package. To "mask the system USE flag" on libxcrypt you would put this in /etc/portage/package.use.mask: sys-libs/libxcrypt system > 3. "mask >=virtual/libcrypt-2" > Like, ">=virtual/libcrypt-2" into /etc/portage/package.accept_keywords, just like that? To mask a package, you put it in /etc/portage/package.mask. Exactly as you write it here, but in a different file. > 4. But virtual/libcrypt:0/1 is not masked (to my knowledge). It is masked here. To unmask it, you could in /etc/portage/package.unmask put something like this: =virtual/libcrypt-1-r1 Regards, Arve
