Brian Harring wrote:
Custom repository is how I intended to implement this; the upshot of
the version translation is that the resultant vdb version is managable
by any PM, regardless if they support -live, which 'generated' the
ebuild.
Presuming svn python bindings aren't as sucky as I recall, tempted to
take a thwack at it over the weekend.
Would be great =)
One thing that would need ironing out for such a proposal is how to
mark in the template metadata variation dependant upon vcs exceeding a
certain level- example would be,
< revno 300
RDEPEND='=dev-lang/python-2.4*'
= revno 300
RDEPEND='>=dev-lang/python-2.5'
That would be quite tricky and I'm not sure how many time it will be
useful since we don't know the future this well ^^;
I'd leave this part out for now.
One other thing that needs discussion imo, is how such a scheme would
work for non integer based revnos- git for example, which is reliant
on a hash (just the hash, afaik).
The revision has to be stored inside the generated ebuild so all you
need to have is:
- a way to know the revision you are checking out
- a way to store such revision withing the ebuild
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@lists.gentoo.org mailing list
