Re: [gentoo-dev] Re: Live source based ebuild proposals

[Ciaran McCreesh <ciaran.mccreesh@googlemail.com>]

[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

On Fri, 13 Feb 2009 23:17:03 +0100
Luca Barbato <lu_zero@gentoo.org> wrote:
> Ciaran McCreesh wrote:
> > No, but something can represent the most commonly used models. We
> > can't do -scm packages for upstreams that do utterly crazy stuff
> > anyway, so we'll stick to the reasonably sane ones.
> 
> So we stick to a subset we assume is what we'd expect from upstream.

Yupyup. That was what we had in mind when we worked out -scm.

> > Topic branches can be covered by use flags.
> 
> So I cannot track mob, master and devel at the same time with -scm 
> alone, I need to get useflag change deeply the ebuild behavior.

If you're looking to track topics rather than versions, yes. Using
versions to track topics gets extremely messy.

> > How do I track an upstream who has a 0.34 branch (which is equal to
> > or ahead of the most recent 0.34.x release)  a 0.36 branch (which
> > is equal to or ahead of the most recent 0.36.x release)
> 
> In those cases is enough take the package version and add one w/out 
> requiring any additional version component...

Be specific. Explain how this works when, say, 0.34.4 is current, you
have a 0.34.5_live and 0.34.5 comes out.

> > and a master branch (which is ahead of any release) using the live
> > property?
> 
> The current versioning alone cannot do it cleanly.

Hence -scm...

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]