On 04/25/2012 09:44 PM, Ryan Hill wrote: > On Wed, 18 Apr 2012 22:41:39 +0100 > David Leverton <levert...@googlemail.com> wrote: > >> The point I was trying to get at was that it seems a bit heavyweight to >> rely on a whole eclass for a minor use-case, as well as a bit >> error-prone to expect people to remember it every time, but maybe that's >> the least bad option after all.... > > Yeah the whole idea here was to make user patches available without ebuild > modifications or eclass dependence.
Using the "apply_user_patches_here" approach [1] that Ciaran suggested, the ebuild wouldn't need any modification unless it overrides default_src_prepare. There is not necessarily any "eclass dependence", though the ebuild may call eclass functions such as eautoreconf when necessary. [1] http://archives.gentoo.org/gentoo-dev/msg_c228be85e0c4e577ad194e6004d59062.xml -- Thanks, Zac
