[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev]  Re: When the version scheme changes
From:       "Marijn Schouten (hkBst)" <hkBst () gentoo ! org>
Date:       2008-06-30 0:22:10
Message-ID: 48682732.8010703 () gentoo ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duncan wrote:
> "Marijn Schouten (hkBst)" <hkBst@gentoo.org> posted
> 4867B636.9080004@gentoo.org, excerpted below, on  Sun, 29 Jun 2008
> 18:20:06 +0200:
> 
>> Why can't portage use its own variables and export these with an initial
>> value but not use them further?
> 
> One way of looking at is that these /are/ the PM's own variables, simply 
> exposed read-only to make life simpler.  There's nothing you can't do by 
> setting your own variables initially equal to the read-only vars and 
> modifying them as you wish, that you could do if the PM exported them 
> writable but ignored any rewritten values itself.  Either a read-only 
> variable works fine, or a rewritable value then ignored by the PM 
> wouldn't work either.

That would work but it would require writing ebuilds in a funny way and would
unexpectedly break when someone DID improperly use the non-writable variables
for anything else than that initial copying. It's really not a solution, because
since there are no guarantees you still have to check all the code and can't do
automatic reversioning. Also doing this would basically be the same as manually
reversioning the entire tree.

Marijn

- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhoJzIACgkQp/VmCx0OL2x4wgCfUoPNEtFWvV/PhIlBk05Cf2FR
rwoAoMlOTrgtoujSqJB5Az1wDSCVXFMB
=I1/q
-----END PGP SIGNATURE-----
-- 
gentoo-dev@lists.gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]