| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Marius Mauch wrote: |
| 5 |
> On Sun, 29 Jun 2008 18:20:06 +0200 |
| 6 |
> "Marijn Schouten (hkBst)" <hkBst@g.o> wrote: |
| 7 |
> |
| 8 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
| 9 |
>> Hash: SHA1 |
| 10 |
>> |
| 11 |
>> Marius Mauch wrote: |
| 12 |
>>> On Sun, 29 Jun 2008 15:52:37 +0200 |
| 13 |
>>> "Marijn Schouten (hkBst)" <hkBst@g.o> wrote: |
| 14 |
>>> |
| 15 |
>>>> -----BEGIN PGP SIGNED MESSAGE----- |
| 16 |
>>>> Hash: SHA1 |
| 17 |
>>>> |
| 18 |
>>>> Bo Ørsted Andresen wrote: |
| 19 |
>>>>> On Saturday 28 June 2008 17:03:13 Marijn Schouten (hkBst) wrote: |
| 20 |
>>>>>> PV=${PV/0./} |
| 21 |
>>>>>> |
| 22 |
>>>>>> to that new ebuild. This is the cleanest way to do it and doesn't |
| 23 |
>>>>>> require any variable name changes or any other changes to the |
| 24 |
>>>>>> ebuild regardless of what it does. Unfortunately it is also |
| 25 |
>>>>>> illegal per current PMS as PV is a read-only variable. Right now |
| 26 |
>>>>>> I feel that the gain of having PV read-only (catch a few bugs?) |
| 27 |
>>>>>> is much lower than the pain (extensive ebuild-dependend changes |
| 28 |
>>>>>> when the version scheme changes). Please comment. |
| 29 |
>>>>> I don't really see how making PV not read-only is any easier than |
| 30 |
>>>>> using MY_PV. Did you expect changing PV to magically change P, PVR |
| 31 |
>>>>> and PF too? |
| 32 |
>>>> If we can agree to have those values writable we could define a |
| 33 |
>>>> function that will handle resetting all those too. |
| 34 |
>>> Not going to happen. These variables are used internally by portage |
| 35 |
>>> in various ways, and making their content inconsistent with the |
| 36 |
>>> version in the filename is likely to cause subtle bugs and/or weird |
| 37 |
>>> behavior. Besides, you've yet to explain the benefit of it, short |
| 38 |
>>> of avoiding a simple replace operation in an ebuild, and the given |
| 39 |
>>> use case isn't all that common anyway. |
| 40 |
>> Why can't portage use its own variables and export these with an |
| 41 |
>> initial value but not use them further? |
| 42 |
> |
| 43 |
> Because there is no need to create even more variables when there is |
| 44 |
> absolutely no benefit. |
| 45 |
|
| 46 |
The benefit is being able to automatically reversion an ebuild. Reversioning may |
| 47 |
not be necessary very often, but it's annoying when it is and there is no good |
| 48 |
reason that it should. There is no benefit in keeping the version variables |
| 49 |
read-only. |
| 50 |
|
| 51 |
Marijn |
| 52 |
|
| 53 |
- -- |
| 54 |
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML |
| 55 |
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode |
| 56 |
-----BEGIN PGP SIGNATURE----- |
| 57 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 58 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 59 |
|
| 60 |
iEYEARECAAYFAkhn5XkACgkQp/VmCx0OL2xBgwCfbOtDaJ27kj1A2CbO95dkrkZb |
| 61 |
x0MAn1usfmfaktYA83MoiukBvlXIuuUN |
| 62 |
=BQs/ |
| 63 |
-----END PGP SIGNATURE----- |
| 64 |
-- |
| 65 |
gentoo-dev@l.g.o mailing list |
Archives