On 04/27/2012 11:57 AM, Michał Górny wrote:
> On Fri, 27 Apr 2012 20:01:15 +0200
> Ulrich Mueller <email@example.com> wrote:
>>>>>>> On Fri, 27 Apr 2012, Zac Medico wrote:
>>> Since we've managed to survive up to this point without such a
>>> feature, I think it's worth the wait roll it into EAPI 5 and have a
>>> clean solution that doesn't rely on package manager interaction with
>>> eclasses. If we quickly draft an EAPI 5 spec, there's still have
>>> time to have it approved at the next council meeting.
>> Did I get it right, you are thinking about a special EAPI only for
>> user patches? I'd say that the feature is not important enough to
>> justify that.
> +1. Either we use EAPIs with some thinking or just drop that concept
> and move on to something else.
> There is a number of features waiting for new EAPI, and noone yet even
> considered them. But when it comes to marginal feature which many of
> devs don't even accept, it's enough to quickly release a new EAPI which
> most of the tree won't support.
The fact that it's a "marginal feature" is exactly why I don't think it
justifies adding a quick and dirty hack that introduces an interaction
between the package manager an eclass function like epatch_user.
On the other hand, if it's important enough to justify a quick and dirty
hack in the package manager, then I'd argue that it's also important
enough to justify a quick and clean EAPI bump.