| 1 |
Here's my old proposal: https://bugs.gentoo.org/show_bug.cgi?id=526456 |
| 2 |
|
| 3 |
Dnia 19 września 2015 14:59:35 CEST, konsolebox <konsolebox@×××××.com> napisał(a): |
| 4 |
>On Sat, Sep 19, 2015 at 6:55 PM, Michał Górny <mgorny@g.o> |
| 5 |
>wrote: |
| 6 |
>> Dnia 19 września 2015 12:27:32 CEST, konsolebox |
| 7 |
><konsolebox@×××××.com> napisał(a): |
| 8 |
>>>On Sat, Sep 19, 2015 at 4:01 PM, Michał Górny <mgorny@g.o> |
| 9 |
>>>wrote: |
| 10 |
>> Which one is simpler: |
| 11 |
>> |
| 12 |
>> 1. _pre, _alpha, _beta, _rc... is earlier than no suffix, _p is newer |
| 13 |
>than no suffix, |
| 14 |
>> |
| 15 |
>> 2. ~ is earlier than no suffix? |
| 16 |
>> |
| 17 |
> |
| 18 |
>Ok I have to admit that no. 2 is simpler. It's less descriptive and |
| 19 |
>requires general or specific guidelines on representing common |
| 20 |
>suffixes, but it allows more flexibility. I actually had the idea |
| 21 |
>earlier of using _pre but using a symbol is more appropriate. Besides |
| 22 |
>_pre already has a position which is > _beta and < _rc. |
| 23 |
> |
| 24 |
>So what would pkg-1.4_alpha1_p20 look like if you convert it to a form |
| 25 |
>that uses ~? |
| 26 |
|
| 27 |
You shouldn't start with old gentoo version but with whatever upstream uses. The goal is that the scheme is really upstream friendly. |
| 28 |
|
| 29 |
So Python-3.5.0a2 would be 3.5.0~a2. We just add the tilde to indicate it's alpha-a and not post-version a. Then, instead of full alpha/beta substitution we just strip the tilde. |
| 30 |
|
| 31 |
So in your case, it could be 1.4~alpha1_p20, or 1.4~a1_20, or… |
| 32 |
|
| 33 |
> |
| 34 |
>Also what about if the package has a custom "newer than no suffix" |
| 35 |
>suffix used like pkg-1.4-sr5-p20? |
| 36 |
|
| 37 |
Well, sr would be used as letter version component but it shouldn't hurt. |
| 38 |
|
| 39 |
We could even extend this to allow multiple tildes and add another symbol that evaluates as higher than any version component. |
| 40 |
|
| 41 |
> |
| 42 |
>> Because you ignored the part explaining it. Any change to versions is |
| 43 |
>a breaking change. |
| 44 |
> |
| 45 |
>Well just now I don't really care about it anymore. Your idea is more |
| 46 |
>on adding another universal symbol to be used for any custom suffix. |
| 47 |
>Mine was more on the algorithm. I actually just found out that having |
| 48 |
>a finite number of components is a mistake and forcing _p to occur |
| 49 |
>after other suffixes is wrong. I also just found a better way which |
| 50 |
>may apply to any EAPI. Because of this I think whether the spec gets |
| 51 |
>changed or not no longer matters to me. Perhaps I'd just post my |
| 52 |
>complete idea on how to efficiently process version strings somewhere. |
| 53 |
>Anyway I already shared the basic concepts of it here. |
| 54 |
|
| 55 |
-- |
| 56 |
Best regards, |
| 57 |
Michał Górny |
Archives