1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Duncan wrote: |
5 |
> "Marijn Schouten (hkBst)" <hkBst@g.o> posted |
6 |
> 4867B636.9080004@g.o, excerpted below, on Sun, 29 Jun 2008 |
7 |
> 18:20:06 +0200: |
8 |
> |
9 |
>> Why can't portage use its own variables and export these with an initial |
10 |
>> value but not use them further? |
11 |
> |
12 |
> One way of looking at is that these /are/ the PM's own variables, simply |
13 |
> exposed read-only to make life simpler. There's nothing you can't do by |
14 |
> setting your own variables initially equal to the read-only vars and |
15 |
> modifying them as you wish, that you could do if the PM exported them |
16 |
> writable but ignored any rewritten values itself. Either a read-only |
17 |
> variable works fine, or a rewritable value then ignored by the PM |
18 |
> wouldn't work either. |
19 |
|
20 |
That would work but it would require writing ebuilds in a funny way and would |
21 |
unexpectedly break when someone DID improperly use the non-writable variables |
22 |
for anything else than that initial copying. It's really not a solution, because |
23 |
since there are no guarantees you still have to check all the code and can't do |
24 |
automatic reversioning. Also doing this would basically be the same as manually |
25 |
reversioning the entire tree. |
26 |
|
27 |
Marijn |
28 |
|
29 |
- -- |
30 |
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML |
31 |
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode |
32 |
-----BEGIN PGP SIGNATURE----- |
33 |
Version: GnuPG v2.0.9 (GNU/Linux) |
34 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
35 |
|
36 |
iEYEARECAAYFAkhoJzIACgkQp/VmCx0OL2x4wgCfUoPNEtFWvV/PhIlBk05Cf2FR |
37 |
rwoAoMlOTrgtoujSqJB5Az1wDSCVXFMB |
38 |
=I1/q |
39 |
-----END PGP SIGNATURE----- |
40 |
-- |
41 |
gentoo-dev@l.g.o mailing list |