| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Fri, 13 Feb 2009 23:17:03 +0100 |
| 3 |
> Luca Barbato <lu_zero@g.o> wrote: |
| 4 |
>> Ciaran McCreesh wrote: |
| 5 |
>>> No, but something can represent the most commonly used models. We |
| 6 |
>>> can't do -scm packages for upstreams that do utterly crazy stuff |
| 7 |
>>> anyway, so we'll stick to the reasonably sane ones. |
| 8 |
>> So we stick to a subset we assume is what we'd expect from upstream. |
| 9 |
> |
| 10 |
> Yupyup. That was what we had in mind when we worked out -scm. |
| 11 |
> |
| 12 |
>>> Topic branches can be covered by use flags. |
| 13 |
>> So I cannot track mob, master and devel at the same time with -scm |
| 14 |
>> alone, I need to get useflag change deeply the ebuild behavior. |
| 15 |
> |
| 16 |
> If you're looking to track topics rather than versions, yes. Using |
| 17 |
> versions to track topics gets extremely messy. |
| 18 |
> |
| 19 |
>>> How do I track an upstream who has a 0.34 branch (which is equal to |
| 20 |
>>> or ahead of the most recent 0.34.x release) a 0.36 branch (which |
| 21 |
>>> is equal to or ahead of the most recent 0.36.x release) |
| 22 |
>> In those cases is enough take the package version and add one w/out |
| 23 |
>> requiring any additional version component... |
| 24 |
> |
| 25 |
> Be specific. Explain how this works when, say, 0.34.4 is current, you |
| 26 |
> have a 0.34.5_live and 0.34.5 comes out. |
| 27 |
> |
| 28 |
>>> and a master branch (which is ahead of any release) using the live |
| 29 |
>>> property? |
| 30 |
>> The current versioning alone cannot do it cleanly. |
| 31 |
> |
| 32 |
> Hence -scm... |
| 33 |
|
| 34 |
that cannot do as well for more than a single target w/out using use flags. |
| 35 |
|
| 36 |
Then if you continued to read you'll notice that |
| 37 |
|
| 38 |
Luca Barbato wrote: |
| 39 |
> The same trick you'd use to track any number of independent branches |
| 40 |
> ahead any release could be used with the current versioning system to |
| 41 |
> archive the same result: use flags triggering the live property and |
| 42 |
> redefining the source accordingly (use live-master, use live-pu, use |
| 43 |
> live-mob) in every ebuild for said package. |
| 44 |
> |
| 45 |
> |
| 46 |
> So the bare minimum to keep the tree w/out "hand made infinity" (-9999) |
| 47 |
> is just use flags and property live as you just stated here, no strict |
| 48 |
> need for -scm for such task. I checked with zmedico and PROPERTIES |
| 49 |
> support conditionals so that is the _bare_ minimum to archive the use |
| 50 |
> case "I want to track a/any number of non version branch of a/any target |
| 51 |
> source controlled tree from upstream" |
| 52 |
|
| 53 |
|
| 54 |
-- |
| 55 |
|
| 56 |
Luca Barbato |
| 57 |
Gentoo Council Member |
| 58 |
Gentoo/linux Gentoo/PPC |
| 59 |
http://dev.gentoo.org/~lu_zero |
Archives