Re: Making user patches globally available

Zac Medico wrote:
> Also, maybe apply_user_patches_here should have a special return value
> if there are no patches to be applied? That way, src_prepare can avoid
> an eautoreconf call if there are no patches.

Does that imply that every ebuild for an autotools-based package would
be expected to have an "apply_user_patches_here && eautoreconf" line,
just in case the user might want to add custom patches?  It could be
exported by autotools.eclass, but even so, requiring every autotools
ebuild to inherit the eclass even if it doesn't have any effect by
default seems a bit unfortunate.