1 |
On 29 June 2012 17:32, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
> |
3 |
> EUSCAN_VERSION=0.71 |
4 |
> |
5 |
> I don't know how difficult that would be for euscan to pickup on, but |
6 |
> since this would have no bearing on actual package behavior, only on |
7 |
> euscan, I'd guess it shouldn't require going thru the formal PMS process, |
8 |
> tho specifying it well enough to know whether it can be a function or |
9 |
> must be a straight variable assignment, etc, as well as whether quotes |
10 |
> are required or not, would be useful, and that's normally part of the PMS |
11 |
> process so at least getting input from them would be useful. |
12 |
> |
13 |
> Alternatively, define some formula that can be placed in the package's |
14 |
> metadata.xml. That's perhaps a better functionality match (we're talking |
15 |
> about metadata, after all), but getting a formula that can deal with all |
16 |
> the corner-cases is likely to be more difficult (and take longer) than |
17 |
> simply specifying a variable to be defined for each ebuild that euscan |
18 |
> can't immediately get correct. |
19 |
|
20 |
The problem is with this approach, some devs will want to set |
21 |
EUSCAN_VERSION automagically using mangling $PV |
22 |
|
23 |
As it is, we *already* have something equivalent to EUSCAN_VERSION for |
24 |
things derived from perl-module.eclass, MODULE_VERSION= |
25 |
|
26 |
Its not 1:1 identical to the intent of EUSCAN_VERSION, MODULE_VERSION |
27 |
is only really required in the generation of SRC_URI , but because of |
28 |
this, there is a loose MODULE_VERSION <-> distfile mapping, and a much |
29 |
looser $PV <-> MODULE_VERSION association. |
30 |
|
31 |
Sure, its fine for MODULE_VERSION to be made by mangling $PV, but the |
32 |
problem is that the *reason* people mangle $PV to make MODULE_VERSION |
33 |
is so they don't have to update MODULE_VERSION manually when bumping |
34 |
the package. |
35 |
|
36 |
Adding a non-bash non-$PV-manglable field EUSCAN_VERSION field will |
37 |
possibly make manually incrementing this value a mandatory thing. |
38 |
|
39 |
Not to mention, if it turns out to be "wrong" on the EUSCAN index, |
40 |
some dev has to drop the change into the repository, do all the |
41 |
manifest updating and commit signing and pushing it to CVS nonsense, |
42 |
when really, its metadata only relevant to euscan, so its really in |
43 |
the wrong place to start with. |
44 |
|
45 |
Having it handled as an exception list on the euscan would be much |
46 |
tidier, and the path from noticing the problem to solving the problem |
47 |
becomes substantially shorter. |
48 |
|
49 |
|
50 |
|
51 |
-- |
52 |
Kent |
53 |
|
54 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, |
55 |
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );" |
56 |
|
57 |
http://kent-fredric.fox.geek.nz |