| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Thu, 26 Feb 2009 20:34:07 +0100 |
| 3 |
> Luca Barbato <lu_zero@g.o> wrote: |
| 4 |
> I'm still waiting for you to answer this: |
| 5 |
> |
| 6 |
>> Be specific. Explain how this works when, say, 0.34.4 is current, you |
| 7 |
>> have a 0.34.5_live and 0.34.5 comes out. |
| 8 |
|
| 9 |
being live working as substitute for 0.34.5_preN (_live) component the |
| 10 |
appearance of 0.34.5 will be higher than those. If we consider the .live |
| 11 |
alternative you'd have 0.34.live that is shadowed only by 0.35.x |
| 12 |
|
| 13 |
That is pretty much the same you get with -scm, what happens is that in |
| 14 |
the case of live template you have portage installing 0.34.5_preN with |
| 15 |
revision informations and adding the template to the "live" set. |
| 16 |
|
| 17 |
This way you can either emerge =0.34.5_preN or emerge @live depending on |
| 18 |
your needs. And you know that what you have installed since the |
| 19 |
information is available. |
| 20 |
|
| 21 |
I replied in the summary but I guess I had been overly implicit =\ |
| 22 |
|
| 23 |
> and this: |
| 24 |
> |
| 25 |
>> How do I track an upstream who has a 0.34 branch (which is equal to or |
| 26 |
>> ahead of the most recent 0.34.x release), a 0.36 branch (which is |
| 27 |
>> equal to or ahead of the most recent 0.36.x release) and a master |
| 28 |
>> branch (which is ahead of any release) using the live property? |
| 29 |
|
| 30 |
the live property doesn't tell much about versioning |
| 31 |
so you could use 9999 as the "x" version component or .live or -scm, |
| 32 |
the live property just makes portage aware that the sources are live. |
| 33 |
|
| 34 |
This situation is one in those pkg-scm and pkg.live work better, but |
| 35 |
just for one branch. |
| 36 |
|
| 37 |
As you said you could address the problem using useflags, so you could |
| 38 |
by extension you can use the same way to address the single case in |
| 39 |
proposals not supporting the tip of a single non version branch as well: |
| 40 |
|
| 41 |
have the all the ebuilds in a package having IUSE=-live that if enabled |
| 42 |
triggers the live property and changes the src_uri to the live branch |
| 43 |
you desire. |
| 44 |
|
| 45 |
Not exactly the nicest thing but having portage highlighting the case of |
| 46 |
live ebuilds on -p would maybe partially address it. |
| 47 |
|
| 48 |
Again it had been answered in the summary anyway. |
| 49 |
|
| 50 |
lu |
| 51 |
|
| 52 |
-- |
| 53 |
|
| 54 |
Luca Barbato |
| 55 |
Gentoo Council Member |
| 56 |
Gentoo/linux Gentoo/PPC |
| 57 |
http://dev.gentoo.org/~lu_zero |
Archives