Re: [gentoo-user] Is there a way to keyword a whole overlay as ~arch ?

[Michael Higgins]

On Sun, 26 Jan 2014 20:14:17 -0500
Michael Orlitzky <mjo@g.o> wrote:

> On 01/26/2014 05:12 PM, Thanasis wrote:
> > I am following stable (ACCEPT_KEYWORDS="amd64").
> > In order to install the "mate" desktop I need to install the mate
> > overlay and keyword all its packages as ~amd64.
> > Is there a way to do it easily for the whole overlay?
> >
>
> 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. 

(Apologies in advance for the noise.)

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...

I suppose it should be printed in red "use if you know what it
means", kind of thing. I can see it being a PITA if it breaks stuff in
the main gentoo tree.


. . .

FWIW, I tried adding that incantation and emerging world, which gave no
changes to my install.

Then I tried:
emerge -av dev-perl/Catalyst-Model-DBIC-Schema

(Which created a bloated keyword file on my other machine.)

This time, it only wants to unmask things perl in the gentoo tree...
but --autounmask-write proposes to list every overlay dep as a comment.

Ugh.

Before, I'd do something like:

mv /etc/portage/package.accept_keywords ~/
mkdir /etc/portage/package.accept_keywords
cp 
package.accept_keywords /etc/portage/package.accept_keywords/99_portage
eix -c --only-in-overlay 0 -C dev-perl|grep '(~' |cut -d ' '
-f 2  | while read a ; do echo $a ~x86 ;done
>  /etc/portage/package.accept_keywords/00_perl

emerge -auDNtv world

Nothing to merge; quitting.

... Which I did. Then /me thinks, for a change.

If */*::overlay-name ~amd64, then:

dev-perl/*::gentoo ~amd64 should work too.

Now, 

emerge -av dev-perl/Catalyst-Model-DBIC-Schema

Gives:

Total: 37 packages (34 upgrades, 3 new), Size of downloads: 5,905 kB

Would you like to merge these packages? [Yes/No] 

And no guff from portage. OMG, what a treat. I wept.

. . .

So wow, if I'd known about that before now, it would have saved me
hours, if not days, worth of hassle.

I think that should be the recommendation for anyone who installs the
perl overlay. Maybe I'm crazy, but it seems to DWIW.

Thanks Michael. Very helpful to know, at least. Does anyone who may
have read this far think this would be a good thing to mention from the
start for a new user of an overlay, like echoed at the end of emerging
layman, or adding a new overlay?

And, yes, it's a full moon, so I'm posting to the list. As is my
habit. ;-)

Cheers [I recommend Flat Tail "seriously budget" barley wine],

- mykhyggz (who lost his .sig)