public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: gentoo-doc@lists.gentoo.org
Subject: [gentoo-doc] Portage per-package environment/behavior
Date: Wed, 28 Dec 2011 11:14:49 +0100	[thread overview]
Message-ID: <20111228101449.GA912@siphos.be> (raw)

Hi guys,

I noticed we don't describe in the handbook that Portage can have
per-package environment variables (like CFLAGS) through /etc/portage/env.
This can be even (ab?)used to execute steps before or after specific phases
(based on the EBUILD_PHASE information), something I use for updating IDS
systems (postinst/prerm phase).

But I'm not sure if and where in the handbook this can be positioned best.
The environment variable stuff could be placed in the section on
"Environment Variables", but is quite off from the rest of the content
(since the rest of that chapter has nothing really to do with Portage or
build environments).

"Configuring through Variables" is probably the best location (somewhere in
the beginning as we talk there about Build-specific Options), but I do feel
that this particular feature is already more targeting advanced users, where
the location in the handbook somewhat suggests this for more beginner-like
types.

Perhaps another section in "Working with Portage", called "Advanced Portage
Features" or so? This can then contain the per-package env information, but
also overriding profile information and perhaps others we don't talk about
yet.

Any ideas on this?

	Sven



             reply	other threads:[~2011-12-28 10:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 10:14 Sven Vermeulen [this message]
2011-12-28 17:20 ` [gentoo-doc] Portage per-package environment/behavior wireless
2011-12-28 17:47 ` [gentoo-doc] " Duncan
2011-12-28 19:10   ` Sven Vermeulen
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=20111228101449.GA912@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --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