[gentoo-dev] Re: When the version scheme changes
Marijn Schouten (hkBst) [EMAIL PROTECTED] wrote: Marius Mauch wrote: Marijn Schouten (hkBst) [EMAIL PROTECTED] wrote: Marius Mauch wrote: I don't really see how making PV not read-only is any easier than using MY_PV. Did you expect changing PV to magically change P, PVR and PF too? If we can agree to have those values writable we could define a function that will handle resetting all those too. Not going to happen. These variables are used internally by portage in various ways, and making their content inconsistent with the version in the filename is likely to cause subtle bugs and/or weird behavior. Besides, you've yet to explain the benefit of it, short of avoiding a simple replace operation in an ebuild, and the given use case isn't all that common anyway. Why can't portage use its own variables and export these with an initial value but not use them further? Because there is no need to create even more variables when there is absolutely no benefit. The benefit is being able to automatically reversion an ebuild. Reversioning may not be necessary very often, but it's annoying when it is and there is no good reason that it should. There is no benefit in keeping the version variables read-only. What is so hard about using MY_PV that you want portage to change how it uses versioning internally? It's one assignment and a sed. -- gcc-porting, by design, by neglect treecleaner, for a fact or just for effect wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 signature.asc Description: PGP signature
[gentoo-dev] Re: When the version scheme changes
Marijn Schouten (hkBst) [EMAIL PROTECTED] posted [EMAIL PROTECTED], 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. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: When the version scheme changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
Marijn Schouten (hkBst) [EMAIL PROTECTED] posted
[EMAIL PROTECTED], 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
