| 1 |
Stroller <stroller <at> stellar.eclipse.co.uk> writes: |
| 2 |
|
| 3 |
|
| 4 |
> > If so, may I ask supporters to make the corresponding changes to the |
| 5 |
> > ebuild. |
| 6 |
|
| 7 |
> There's already a bug for this on Gentoo's tracker: |
| 8 |
> https://bugs.gentoo.org/show_bug.cgi?id=524850 |
| 9 |
|
| 10 |
> I think that last comment by Greg Kubaryk about the ebuild being |
| 11 |
> epatch_user enabled means you can just |
| 12 |
> download those two patches (google for 1ff71… and 7df30…) and put them in |
| 13 |
> the right /etc/portage subdirectory to have them applied automatically. |
| 14 |
> Stroller. |
| 15 |
|
| 16 |
|
| 17 |
Well I aware of the movement in EAPI-6 [1] to support user patching. |
| 18 |
|
| 19 |
But, I think Stroller is talking about "epatch_user" doc here ? [2] |
| 20 |
|
| 21 |
|
| 22 |
Another question. How can you tell whether a package (ebuild) supports |
| 23 |
user patching? What EAPI rev did user patching first appear? |
| 24 |
|
| 25 |
And last, can any patch that ends in .patch be applied to the |
| 26 |
intended ebuild or does the gentoo ebuild auther have to put |
| 27 |
some special code into an (EAPI-5) ebuild to facilitate user |
| 28 |
patches? Some docs or general discussion would be keen. Like |
| 29 |
user patches surviving an upgrade of the (patched) package? |
| 30 |
Or what if the next package upgrade includes a better version |
| 31 |
of the patch, but it performs a similar function. Or what if the |
| 32 |
patch you add becomes a stale (version/fork); how do you know or |
| 33 |
do you have to remind yourself to follow the development details |
| 34 |
of that (ebuild) package? |
| 35 |
|
| 36 |
curiously, |
| 37 |
James |
| 38 |
|
| 39 |
|
| 40 |
[1] http://wiki.gentoo.org/wiki/Future_EAPI/EAPI_6_tentative_features |
| 41 |
|
| 42 |
[2] http://wiki.gentoo.org/wiki//etc/portage/patches |
Archives