| 1 |
Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
> On Fri, 13 Jun 2008 10:43:39 +0200 |
| 4 |
> Luca Barbato <lu_zero@g.o> wrote: |
| 5 |
>> Ciaran McCreesh wrote: |
| 6 |
>> > On Thu, 12 Jun 2008 21:40:28 +0200 |
| 7 |
>> > Luca Barbato <lu_zero@g.o> wrote: |
| 8 |
>> >>> * ordering for _pre is wrong. |
| 9 |
>> >> hm? |
| 10 |
>> > |
| 11 |
>> > foo-0.26-live would become foo-0.26_pre1, which would be < 0.26. |
| 12 |
>> > This is clearly wrong. |
| 13 |
>> |
| 14 |
>> No, it is correct and what you want. Upstream is aiming for 0.26, |
| 15 |
>> once 0.26 gets in portage you want to update to the release. |
| 16 |
> |
| 17 |
> A lot of projects work like this: |
| 18 |
> |
| 19 |
> * trunk/ is current development, and is ahead of any release. |
| 20 |
> |
| 21 |
> * branches/0.26/ is forked from trunk/ when 0.26 is released, and is |
| 22 |
> equal to or ahead of any 0.26 release. |
| 23 |
> |
| 24 |
> How does your proposal handle this? |
| 25 |
|
| 26 |
s/_pre/_p ? |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@l.g.o mailing list |
Archives