On Fri, 14 Feb 2014 20:00:47 -0800, Michael Higgins wrote: > > Yep, you just need to know the overlay name. In > > package.accept_keywords: > > > > */*::overlay-name ~amd64 > > > > The "*/*" syntax means any category, any package name. The "::" then > > specifies the repository name. If you don't know the repository name, > > it can often be found in path/to/overlay/profiles/repo_name.
> I wonder, can we get a hint of this function echo-ed at the end of every > new layman install? It would make using, say, perl-experimental, far > less unwieldy than without. It is documented in man portage, in the wildcards subsection of the atom definition part. > I had no idea this was possible, but it seems the only way to use the > overlay without making of mess of package.accept_keywords, which is > what I have had when installing anything useful in the perl development > area. > > Does this make any sense? Do all the overlays work that way, that is, > kw-masking everything so you have to enable the ~arch per package? This > always seemed absurd to me, as I added the overlay, I must have meant > to use it... but anyway... You are running a stable arch, using only ebuilds that have been through Gentoo QA and user testing. Presumably you do that for a reason, so portage suddenly allowing installation of untested packages from a random repository goes against what you have told it you want in make.conf. Adding an overlay to layman does not necessarily mean you want everything that overlay offers. In some cases there will be newer, less tested, versions of packages you already have installed, packages you may not want randomly updated. The only way portage can know what you want is if you tell it so, the current approach is the safest, it only breaks what you tell it to break. This is Gentoo where you do the thinking and the system does what you tell it (which may not always be what you want). -- Neil Bothwick WinErr 00A: Promotional literature overflow - Mailbox full
signature.asc
Description: PGP signature
