| 1 |
On Tue, 04 Aug 2009 18:31:21 +0200 |
| 2 |
Sebastian Pipping <webmaster@××××××××.org> wrote: |
| 3 |
> implementation |
| 4 |
> ============== |
| 5 |
> |
| 6 |
> a few variables in portage that do not have a direct equivalent in |
| 7 |
> paludis: |
| 8 |
> |
| 9 |
> - ACCEPT_KEYWORDS: deduce from '*/*' line in platforms.conf? |
| 10 |
|
| 11 |
What do you need this for? It's a fairly meaningless bit of information |
| 12 |
now that there's package.keywords for Portage. |
| 13 |
|
| 14 |
> - ARCH: deduce from CHOST and deduced ACCEPT_KEYWORDS |
| 15 |
|
| 16 |
You can get the value of the ARCH var used to install Paludis. |
| 17 |
|
| 18 |
> - SYNC: not deducable |
| 19 |
|
| 20 |
Sure it is. Ask a repository if it has a metadata key named 'sync', and |
| 21 |
use what it returns. |
| 22 |
|
| 23 |
> atoms in paludis seem to be a superset of portages. if so that would |
| 24 |
> not cause any trouble so far. |
| 25 |
|
| 26 |
Not quite. We treat =* things differently depending upon context (they |
| 27 |
mean the thing that makes sense when used in user config files, and |
| 28 |
only emulate Portage weirdness when handling EAPI controlled things). |
| 29 |
|
| 30 |
> any technical differences that you consider to become a problem? |
| 31 |
|
| 32 |
You seem to be hitting upon it with the 'global configuration' things. |
| 33 |
Pretty much everything in Paludis is a per-package setting, with |
| 34 |
wildcards being how you apply settings broadly. |
| 35 |
|
| 36 |
-- |
| 37 |
Ciaran McCreesh |
Archives