1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Piotr Jaroszyński wrote: |
5 |
> 2009/5/28 Ulrich Mueller <ulm@g.o>: |
6 |
>>>>>>> On Thu, 28 May 2009, Tiziano Müller wrote: |
7 |
>>>> ${PORTDIR}/app-misc/foo/foo-1a_live.ebuild |
8 |
>>>> ${PORTDIR}/app-misc/foo-1a/foo-1a-live.ebuild |
9 |
>>> you probably mean: |
10 |
>>> ${PORTDIR}/app-misc/foo-1a/foo-1a.live.ebuild |
11 |
>> No, I mean what I had written, namely to use an underscore as |
12 |
>> separator, i.e., "_live". But when the version is just "live" alone, |
13 |
>> one would suppress the underscore for aesthetic reasons, i.e. instead |
14 |
>> of "foo-1a-_live" it would be "foo-1a-live". |
15 |
>> |
16 |
>>> but how would their vdb or binpkg names be unique? |
17 |
>>> vdb for example: |
18 |
>>> app-misc/foo-1a_live for app-misc/foo |
19 |
>> PN=foo, PV=1a_live => app-misc/foo-1a_live |
20 |
>> |
21 |
>>> app-misc/foo-1a_live for app-misc/foo-1a |
22 |
>> PN=foo-1a, PV=live => app-misc/foo-1a-live |
23 |
>> |
24 |
>>> am I missing something? |
25 |
>> Everything is easy, if you keep the following rule in mind: |
26 |
>> |
27 |
>>>> With our current versioning scheme the rule is very simple: ${P} is |
28 |
>>>> split into ${PN} and ${PV} at the last hyphen. This can be done in |
29 |
>>>> a straight forward way by regexp matching, and I would really hate |
30 |
>>>> to lose this nice property. |
31 |
>>> I don't understand why this property is important. Can you please |
32 |
>>> explain? |
33 |
>> See above, it automatically avoids any ambiguities in splitting P into |
34 |
>> PN and PV. And look at function "pkgsplit" in Portage: It can just |
35 |
>> treat PV as an opaque string. |
36 |
>> |
37 |
>> What would be the advantage to use a hyphen instead of an underscore? |
38 |
> |
39 |
> Mainly the thing you observed yourself - foo_live is a bit |
40 |
> inconsistent with current versions. |
41 |
|
42 |
Ulrich is proposing foo-live if live is the entire version, foo_live is not a |
43 |
legal `package name and version'. (It could be a package name though.) |
44 |
|
45 |
> The case you mention can be avoided with another restriction in PMS. |
46 |
> Buut we might as well go all the way and change the version separator |
47 |
> to -- or something, which would be the most flexible. |
48 |
|
49 |
That would also be a good solution though we don't seem to need it yet. It would |
50 |
also entail compatibility issues. |
51 |
|
52 |
Marijn |
53 |
|
54 |
- -- |
55 |
If you cannot read my mind, then listen to what I say. |
56 |
|
57 |
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML |
58 |
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode |
59 |
-----BEGIN PGP SIGNATURE----- |
60 |
Version: GnuPG v2.0.11 (GNU/Linux) |
61 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
62 |
|
63 |
iEYEARECAAYFAkoeqg0ACgkQp/VmCx0OL2zn2gCfZl0knh8Er2x1B8PrbdwWSYHU |
64 |
b/MAnj3pYO2qzXhUx+z1w9Vnrdf2/uJo |
65 |
=EzB3 |
66 |
-----END PGP SIGNATURE----- |