-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James wrote:
> Neil Bothwick writes:
>> cat /etc/portage/sets/kde4.3 >>/etc/portage/package.keywords
>> Or make package.keywordsa directory and simply put a copy of the sets
>> file in there (or a symlink to the sets file). This is the more
>> manageable option.
>
> Interesting approach. I usually like to follow the gentoo recommended
> practices. I get the feeling that "sets" via portage 2.2 is very
> much a work in progress. So which of these approaches is likely
> to become the de'facto method?
>
> Also, I omitted the "~amd64" at the end of all of those manual
> entries into my package.keywords file. It work without them.
> So my question is the "-amd64" entry on every line of my package.keywords
> deprecated now with portage 2.2?
>
>
> James
>
If you are using the kde-testing overlay, there are files that you can
symlink under /etc/portage/package.{keywords,unmask}/ to unmask/keyword
particular versions of KDE. Note also that "any file in [/etc/portage]
that begins with 'package.' can be more than just a flat file. If it is
a directory, then all the files in that directory will be sorted in
ascending alphabetical order by file name and summed together as if it
were a single file" (from portage(5)). To be precise, it can be an
entire directory tree, and still work the same way.
A line in package.keywords without any KEYWORDS implies "~${ARCH}"
(again, see portage(5)).
With the exception of sets and FEATURES=preserved-libs, everything in
portage-2.2 is in portage-2.1.6.*, which is now stable just about
everywhere, so this behavior is at least that old (although I believe it
has been around longer).
- --
ABCD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkm1awcACgkQOypDUo0oQOpvhgCdEAKRJp1kSFoff++jTn+JQYvp
VZ8An0/7OMDSrfddocWGkJFiArV4D8tZ
=gruJ
-----END PGP SIGNATURE-----
