On 2017-11-24 08:32, Neil Bothwick wrote:
> > Package P bypasses applying user patches (by not calling
> > default_src_prepare). I have patches I need to apply to P, and in
> > this case I really don't want to fork the ebuild. So, I'm hell bent
> > on doing it the hacky way with /etc/portage/bashrc (which, IIRC, I
> > have been told on this list not to do, but now I don't have much
> > choice).
>
> You do have a choice, use /etc/portage/env. here's one I have to patch
> a specific version of a package
>
> % cat env/app-cdr/cdrdao-1.2.3
> post_src_unpack() {
> cd "${S}"
> epatch_user
> }
Again IIRC, when I tried using env for a similar purpose, it didn't work
at all, it seemed the only things valid in those files were variable
assignments. If possible, I would of course much prefer this way, as is
avoids an ugly switch on the package name.
Do you know what I could've been doing wrong? I think I brought it up
on the list, I'll try to dig up the thread.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.
