public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] per-package environment variables.
Date: Wed, 01 Sep 2004 11:46:37 -0700	[thread overview]
Message-ID: <20040901184637.GA7518@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <20040901184257.GA4403@CogES>

[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]

On Wed, Sep 01, 2004 at 08:42:57PM +0200, aye wrote:
> On Wed, Sep 01, 2004 at 08:59:11AM -0700, Robin H. Johnson wrote:
> > Your setup here could be better solved with portage recognizing groups
> > of packages - both predefined groups 'system' and custom groups.
> > 
> > Eg you can replace everything with one line:
> > package-group/system low_c_flags
> > 
> > And that would compile everything portage considers as system with the
> > environment from low_c_flags.
> > 
> yep - it's also good idea, however i'd still have to declare 'system'
> class somewhere. the one used in profile isn't good for me (for example
> x11 is in profile), but you've ofcourse right - it would look nicer if i
> had just package-group/system and profile, which satisfy me.
Somebody else was ahead of us on it, but I don't know how much progress
was made on it:
http://www.gentoo.org/proj/en/glep/glep-0021.html

Coredumb notes that USE flags for sets could prove a problem, and
unfortunately the same problem would effect this package.env proposal.
Namely, if you have two entries:
virtual-set/foo env1
virtual-set/bar env2
some-cat/foo env3

some-cat/foo is present is both sets.
If some-cat/foo is being merged directly, the settings from the sets
will be totally ignored - even if we could detect them, which one would
we use? There are a couple of other similar problem cases with sets and
any of the portage settings that might be applied per-package :-(.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2004-09-01 21:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 22:26 [gentoo-dev] per-package environment variables Antst GD
2004-08-31 22:34 ` Mike Frysinger
2004-08-31 22:44 ` Antst GD
2004-09-08 18:19   ` Ned Ludd
2004-08-31 23:28 ` Mike Frysinger
2004-09-01  0:00   ` Anton Starikov
2004-09-01  0:13   ` Anton Starikov
2004-09-01  3:05   ` Olivier Fisette
2004-09-01 11:08     ` Anton Starikov
2004-09-01 15:53       ` Robin H. Johnson
2004-09-01 19:56       ` Olivier Fisette
2004-09-01 22:39         ` Anton Starikov
2004-09-02 22:49         ` Anton Starikov
2004-09-02 23:30           ` Olivier Fisette
2004-09-03  1:36             ` Anton Starikov
2004-09-03  1:35               ` Robin H. Johnson
2004-09-03  2:05               ` Olivier Fisette
2004-09-03  2:53                 ` Anton Starikov
2004-09-01  0:26 ` Nicholas Jones
2004-09-01  0:51   ` Anton Starikov
2004-09-01 14:02 ` aye
2004-09-01 14:22   ` Anton Starikov
2004-09-01 15:59   ` Robin H. Johnson
2004-09-01 18:42     ` aye
2004-09-01 18:46       ` Robin H. Johnson [this message]

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=20040901184637.GA7518@curie-int.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-dev@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