Re: [proaudio] busted package.keywords

[Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx>]

On Mi, 14.03.07 10:46 "we are" <gateswideopen@xxxxxxxxx> wrote:

> hey there.
> i have a problem with my portage overlays.
> i have lost control over my /etc/portage/package.keywords file, i used
> to be able to place a -* for my cvs builds but now its as iff postage
> completely ignores my keywords file.
> this went bad when i followed the guide at
> 
> http://gentoo-wiki.com/HOWTO_emerge_e17
> 
> the page tells me to ...
> 
> # emerge layman
> # echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf
> # layman -S
> # layman -f
> # layman -a enlightenment
> # if [ -f /etc/portage/package.keywords ] ; then mv
> /etc/portage/package.keywords /etc/portage/package.keywords_tmp ; fi
> # mkdir -p /etc/portage/package.keywords
> # ln
> -s /usr/portage/local/layman/enlightenment/scripts/package.keywords.livecvs /etc/portage/package.keywords/enlightenment
> # if [ -f /etc/portage/package.keywords_tmp ] ; then mv
> /etc/portage/package.keywords_tmp /etc/portage/package.keywords/common
> ; fi
> 
> 
> which is all fine for the enlightenment overlay but they have moved my
> package.keywords file to /etc/portage/package.keywords/common
> 
> that seems like a good idea but how do i make portage and proaudio
> read this common file so i can go back to normal merging.
> 
> thanks all

Portage will also read in the "common" file. But did you notice the
changes in pro-audio overlay that live CVS ebuilds now need ** and not
-*, means all pro-audio CVS stuff has to be keyworded with **.

Vapier still uses -* for E.

Cheers,
Tom

Attachment: signature.asc
Description: PGP signature