From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Just when is portage/bashrc sourced?
Date: Thu, 23 Nov 2017 17:12:37 -0800 [thread overview]
Message-ID: <20171124011237.27jausp5fmhrr424@matica.foolinux.mooo.com> (raw)
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).
To make it work I need to know how the bashrc file is spliced into the
ebuild. For a given ebuild phase PH, does the bashrc code come before
the rest of PH, after PH, or does it replace PH? wiki and even the dev
guide are silent about this.
--
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.
next reply other threads:[~2017-11-24 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 1:12 Ian Zimmerman [this message]
2017-11-24 1:21 ` [gentoo-user] Just when is portage/bashrc sourced? Michael Orlitzky
2017-11-24 8:32 ` Neil Bothwick
2017-11-24 17:07 ` [gentoo-user] " Ian Zimmerman
2017-11-24 17:12 ` Michael Orlitzky
2017-11-24 22:21 ` Neil Bothwick
2017-11-25 1:56 ` Ian Zimmerman
2017-11-25 8:59 ` Neil Bothwick
2017-11-26 20:24 ` Neil Bothwick
2017-11-27 1:57 ` David Haller
2017-11-27 8:35 ` Neil Bothwick
2017-11-27 12:59 ` Michael Orlitzky
2017-11-27 17:17 ` Ian Zimmerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171124011237.27jausp5fmhrr424@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox