On Tue, 04 Aug 2009 18:31:21 +0200 Sebastian Pipping <[email protected]> wrote: > implementation > ============== > > a few variables in portage that do not have a direct equivalent in > paludis: > > - ACCEPT_KEYWORDS: deduce from '*/*' line in platforms.conf?
What do you need this for? It's a fairly meaningless bit of information now that there's package.keywords for Portage. > - ARCH: deduce from CHOST and deduced ACCEPT_KEYWORDS You can get the value of the ARCH var used to install Paludis. > - SYNC: not deducable Sure it is. Ask a repository if it has a metadata key named 'sync', and use what it returns. > atoms in paludis seem to be a superset of portages. if so that would > not cause any trouble so far. Not quite. We treat =* things differently depending upon context (they mean the thing that makes sense when used in user config files, and only emulate Portage weirdness when handling EAPI controlled things). > any technical differences that you consider to become a problem? You seem to be hitting upon it with the 'global configuration' things. Pretty much everything in Paludis is a per-package setting, with wildcards being how you apply settings broadly. -- Ciaran McCreesh
signature.asc
Description: PGP signature
