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