From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Re: Portage per-package environment/behavior
Date: Wed, 28 Dec 2011 19:10:40 +0000 [thread overview]
Message-ID: <20111228191040.GA10551@gentoo.org> (raw)
In-Reply-To: <pan.2011.12.28.17.47.17@cox.net>
On Wed, Dec 28, 2011 at 05:47:18PM +0000, Duncan wrote:
> IIRC this (and /etc/portage/patches) was originally deliberately kept an
> "undocumented feature", to avoid trouble with missing info in bug
> reports, since emerge info didn't report package specific information.
This "/etc/portage/patches" thingie is something that the ebuilds must
support themselves afaik (call epatch_user), although I can imagine a way to
have it triggered for all systems by fiddling with /etc/portage/env too ;-)
> Now that portage has emerge --info <pkg> and it's what's requested in the
> usual output when a build aborts (tho AFAIK bugzilla still mentions
> emerge info output only), and the logs themselves are rather better at
> reporting user patches (for the patches subdir), that's not so much of a
> problem, and the portage documentation itself mentions both usages of the
> env subdir (tho not the patches subdir since that's still ebuild
> activated).
We might want to catch some bugzie admins then and suggest to update their
page ;-)
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2011-12-28 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 10:14 [gentoo-doc] Portage per-package environment/behavior Sven Vermeulen
2011-12-28 17:20 ` wireless
2011-12-28 17:47 ` [gentoo-doc] " Duncan
2011-12-28 19:10 ` Sven Vermeulen [this message]
2011-12-28 18:01 ` [gentoo-doc] " Matthew Summers
2011-12-29 18:18 ` Sven Vermeulen
2011-12-30 1:56 ` [gentoo-doc] " Duncan
2011-12-30 12:29 ` Sven Vermeulen
2011-12-31 20:16 ` [gentoo-doc] " Sven Vermeulen
2011-12-31 23:41 ` [gentoo-doc] " Duncan
2012-01-01 3:13 ` [gentoo-doc] " Joshua Saddler
2012-01-01 8:59 ` Sven Vermeulen
2012-01-02 18:54 ` Joshua Saddler
2012-01-03 17:33 ` Sven Vermeulen
2012-01-01 9:30 ` [gentoo-doc] " Duncan
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=20111228191040.GA10551@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-doc@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