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