public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] per-package environment variables.
Date: Wed, 01 Sep 2004 08:53:56 -0700	[thread overview]
Message-ID: <20040901155356.GA20759@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <4135AD9B.8090109@ifm.liu.se>

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

On Wed, Sep 01, 2004 at 01:08:11PM +0200, Anton Starikov wrote:
> Olivier Fisette wrote:
> >If we wanted to make things even easier to configure, we could have 
> >something like the following in "/etc/portage/package.env":
> >
> >=app-sci/pymol-0.95* [ CC="gcc" CFLAGS="-O1" ]
> >
> >... were a keyword is replaced by a delimited short bash script that would 
> >be sourced to provide per package env vars. This would avoid having to 
> >create files in "/etc/portage/env.d" which target only one package.
> Anyway, if we going to include both, files and inlined vars, we have to 
> have a bit complicated parser of lines. In such case we even don't need 
> [], we can leave as
> =app-sci/pymol-0.95* gcc_low_opt CC="gcc"
> "=" specify enough that we have inlined expression.
So you want to take out those of us that have strange filenames?
I'd say the inlined case shouldn't be used, but the general idea here is
a good one.

The format definetly should be:
atom list_of_files
As that is the only non-ambiguous way of doing it.

See bug #51552 for more on environment variables in portage.

-- 
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 18:20 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 [this message]
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

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=20040901155356.GA20759@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