Carsten Lohrke wrote: > I don't see the necessity for devs and users would have to look at the > package.mask file regularly to get the information that a package is masked. > If Portage would be that smart to spit out the relevant information on > emerge --sync, a longer period would probably make sense.
Not that I'd care so much whether it's a week or a month (IMO individual depending on ebuild in question) - so just a technical note. Portage 2.1 *does* spit out the relevant info. # emerge -uDpv world These are the packages that would be merged, in order: Calculating world dependencies / !!! Packages for the following atoms are either all !!! masked or don't exist: net-ftp/glftpd ... done! # esearch glftpd [ Results for search key : glftpd ] [ Applications found : 1 ] * net-ftp/glftpd [ Masked ] Latest version available: 2.01 Latest version installed: 1.32 -- jakub
signature.asc
Description: OpenPGP digital signature