On Fri, Jun 13, 2008 at 10:43:39AM +0200, Luca Barbato wrote:
> Anyway pkgcore and portage devs, I'd like your opinion on this point.

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.

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... gets tricky.  I can think of hacks for it, but none I like.  
Alternatively, if there was a way to have seperate templates that are 
selected dependant upon the desired rev, it becomes possible.

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).

Either way, I tend to view it as having a fair bit more control then 
the -scm proposal, although needs fleshing out a bit.

~harring