| 1 |
On 16:42 Sun 07 Nov , Petteri Räty wrote: |
| 2 |
> On 11/06/2010 11:22 AM, Krzysztof Pawlik wrote: |
| 3 |
> > Hello, |
| 4 |
> > |
| 5 |
> > I'm sending this patch for discussion, what it changes? The change is to where |
| 6 |
> > the final clone of repository will be placed, it used to be ${WORKDIR}/${module} |
| 7 |
> > (where module usually is the last component of source URI) to ${WORKDIR}/${P} |
| 8 |
> > (essentially ${S}). This has few effects: |
| 9 |
> > - ebuilds using mercurial.eclass don't need to set S any longer |
| 10 |
> > - mercurial.eclass behaves more like git.eclass |
| 11 |
> > - it breaks all existing ebuilds using this eclass |
| 12 |
> |
| 13 |
> Which means that the doing the chance is not allowed as eclasses must |
| 14 |
> remain backwards compatible. |
| 15 |
|
| 16 |
Is that really still the case now that full environments have been saved |
| 17 |
for a number of years? Clearly breaking things is unacceptable, but I |
| 18 |
could envision someone simultaneously updating the eclass and all |
| 19 |
consumers. |
| 20 |
|
| 21 |
Perhaps you could point me to the appropriate documentation, if any |
| 22 |
exists. |
| 23 |
|
| 24 |
-- |
| 25 |
Thanks, |
| 26 |
Donnie |
| 27 |
|
| 28 |
Donnie Berkholz |
| 29 |
Sr. Developer, Gentoo Linux |
| 30 |
Blog: http://dberkholz.wordpress.com |
Archives