[gentoo-dev] Re: Making user patches globally available

[Nikos Chantziaras <realnc@gmail.com>]

On 27/04/12 17:15, Duncan wrote:
> Zac Medico posted on Thu, 26 Apr 2012 18:41:21 -0700 as excerpted:
>> Having the package manager interact with an eclass function like
>> epatch_user is ugly, and it's unnecessary since we can pull all of the
>> pieces into the package manager in EAPI 5. Any eclasses that currently
>> call epatch_user can have a conditional like this:
>>
>>     if has $EAPI 0 1 2 3 4 ; then
>>       epatch_user
>>     else
>>       apply_user_patches_here
>>     fi
>
> But that doesn't solve the problem of making it globally available, since
> it only applies to packages/eclasses that already call epatch_user for
> EAPIs thru current EAPI-4.
>
> In ordered to make it globally available, it cannot simply be an EAPI-5
> thing, it must apply to all current ebuilds whether they (or an inherited
> eclass) call epatch_user or not.  Which means that conflict with the
> existing epatch_user is unavoidable, since it will either try to run
> twice where it's already called, or it won't run at all where it's not.

According to the source, calling it twice is perfectly safe.