| 1 |
Luca Barbato schrieb: |
| 2 |
> Santiago M. Mola wrote: |
| 3 |
>> On Sat, Jun 14, 2008 at 10:19 AM, Luca Barbato <lu_zero@g.o> |
| 4 |
>> wrote: |
| 5 |
>>> Ryan Hill wrote: |
| 6 |
>>>> I'm guessing the dev would need to change 0.26.live to 0.26.1.live when |
| 7 |
>>>> 0.26 was released. I already need to do this with my live ebuilds. Of |
| 8 |
>>>> course, with some projects you never know if the next version will be |
| 9 |
>>>> 0.26.1, 0.27, or 0.3, or 1.0... |
| 10 |
>>> That's an upstream issue, all we should care is about getting a version |
| 11 |
>>> value that makes sense for us, better if it does for them. |
| 12 |
>>> |
| 13 |
>> |
| 14 |
>> I think upstream use release branches correctly here, and it's the |
| 15 |
>> most widespread use. |
| 16 |
>> |
| 17 |
>> There's some real examples where ".live" = "_pre" has problems. |
| 18 |
>> |
| 19 |
>> * media-video/mplayer: I'd expect 1.0.live to be higher than 1.0_rc2, |
| 20 |
>> but it doesn't. I'd also expect 1.0.live to be higher than 1.0 when |
| 21 |
>> it's released. |
| 22 |
> |
| 23 |
> MPlayer has a psychological issue with 1.0 versioning, still 1.0.live |
| 24 |
> correctly isn't higher than 1.0 |
| 25 |
No, it is not. |
| 26 |
|
| 27 |
Take KDE for example, they have trunk currently, that will become KDE |
| 28 |
4.1.0. When that has been released, there will be a branch 4.1, which is |
| 29 |
ahead of 4.1.0 and will become 4.1.1, then 4.1.2 (when 4.1.1 has been |
| 30 |
released) etc. |
| 31 |
|
| 32 |
In the -scm approach this means: |
| 33 |
trunk = -scm |
| 34 |
4.1 branch = -4.1-scm |
| 35 |
|
| 36 |
With your approach, we would have to fix the version after every 4.1.x |
| 37 |
release. That sounds awful, tbh. So: |
| 38 |
trunk = .live |
| 39 |
4.1 branch = 4.1.1.live (before 4.1.1 has been released) |
| 40 |
4.1 branch = 4.1.2.live (before 4.1.2 has been released) |
| 41 |
4.1 branch = 4.1.3.live (before 4.1.3 has been released) |
| 42 |
... |
| 43 |
-- |
| 44 |
gentoo-dev@l.g.o mailing list |
Archives