1 |
On Sun, 29 Jun 2008 18:20:06 +0200 |
2 |
"Marijn Schouten (hkBst)" <hkBst@g.o> wrote: |
3 |
|
4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
5 |
> Hash: SHA1 |
6 |
> |
7 |
> Marius Mauch wrote: |
8 |
> > On Sun, 29 Jun 2008 15:52:37 +0200 |
9 |
> > "Marijn Schouten (hkBst)" <hkBst@g.o> wrote: |
10 |
> > |
11 |
> >> -----BEGIN PGP SIGNED MESSAGE----- |
12 |
> >> Hash: SHA1 |
13 |
> >> |
14 |
> >> Bo Ørsted Andresen wrote: |
15 |
> >>> On Saturday 28 June 2008 17:03:13 Marijn Schouten (hkBst) wrote: |
16 |
> >>>> PV=${PV/0./} |
17 |
> >>>> |
18 |
> >>>> to that new ebuild. This is the cleanest way to do it and doesn't |
19 |
> >>>> require any variable name changes or any other changes to the |
20 |
> >>>> ebuild regardless of what it does. Unfortunately it is also |
21 |
> >>>> illegal per current PMS as PV is a read-only variable. Right now |
22 |
> >>>> I feel that the gain of having PV read-only (catch a few bugs?) |
23 |
> >>>> is much lower than the pain (extensive ebuild-dependend changes |
24 |
> >>>> when the version scheme changes). Please comment. |
25 |
> >>> I don't really see how making PV not read-only is any easier than |
26 |
> >>> using MY_PV. Did you expect changing PV to magically change P, PVR |
27 |
> >>> and PF too? |
28 |
> >> If we can agree to have those values writable we could define a |
29 |
> >> function that will handle resetting all those too. |
30 |
> > |
31 |
> > Not going to happen. These variables are used internally by portage |
32 |
> > in various ways, and making their content inconsistent with the |
33 |
> > version in the filename is likely to cause subtle bugs and/or weird |
34 |
> > behavior. Besides, you've yet to explain the benefit of it, short |
35 |
> > of avoiding a simple replace operation in an ebuild, and the given |
36 |
> > use case isn't all that common anyway. |
37 |
> |
38 |
> Why can't portage use its own variables and export these with an |
39 |
> initial value but not use them further? |
40 |
|
41 |
Because there is no need to create even more variables when there is |
42 |
absolutely no benefit. |
43 |
|
44 |
Marius |
45 |
-- |
46 |
gentoo-dev@l.g.o mailing list |