Dne sobota 14 Březen 2009 20:32:52 Ciaran McCreesh napsal(a): > Doing this properly is an awful lot of work and a lot trickier than > initially apparent. There was a discussion in #gentoo-council about it > after the last meeting; unfortunately I don't have logs. Hm i try to crawl around if i find some time. Maybe i find them. > > I see the solution as being done in four parts, one after another: > > * Proper ordering for live packages. This is GLEP 54. > > * Allowing installed SCM ebuilds to identify the revision with which > they were built. This isn't overly difficult, once you get around > things like CVS not really having a revision. > > * Allowing SCM ebuilds to identify upfront, and potentially at > --pretend time, with which revision they will be built. This is the > hard part, especially if you want to be able to background fetch them. > > * Allowing user overrides of revisions in a controlled manner. > > In terms of goals, [1] is what I'd consider to be an ideal list. > > Unfortunately, given the difficulty of getting even the first item on > the list implemented, I don't see this going anywhere any time soon for > Gentoo... > > [1]: http://lists.exherbo.org/pipermail/exherbo-dev/2009-March/000409.html
Well for git i am already parsing if the revision changed or not and based on that i log usefull informations for user :] So i guess adding wrapper around remaining relevant phases is just bit coding around. I am sadly not sure how other scms behave and specialy it is sweet overhead in cvs as you say :] But at least for git users it would be nice to have (fdo, kernel, various misc stuff).
signature.asc
Description: This is a digitally signed message part.
