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