public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: aye <aye@gentoo.pl>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] per-package environment variables.
Date: Wed, 1 Sep 2004 16:02:46 +0200	[thread overview]
Message-ID: <20040901140246.GA5942@CogES> (raw)
In-Reply-To: <4134FB0B.9060501@ifm.liu.se>

well - i've got one more idea. all your proposal have one weakness from
my point of view. i've reported bug (and reopened the second one) for
one reason: i want to have some base system compiled in way, which makes
me possibility to run on diffrent procesors (mainly i'm interested in
pentiums and athlons), while the rest of programs should be compiled
with optimalization for my home cpu.
in your solutions i'd have to had a long file looks like it:

category/package1 low_c_flags*
category/package2 low_c_flags
category/package3 low_c_flags
category/package4 low_c_flags
category/package5 low_c_flags
[...]
category/package100 low_c_flags

*low_c_flags is just example - no matter how it'd be called, if it would
be file name or settings or some kind of keyword - it looks ugly. in the
other hand i don't think that anyboby would need more then 3 or 4 sets
of flag. so what i propose is to have a /etc/portage/package.env with
syntax as below:

CFLAGS="-option1 -option2 -option3"
PACKAGES="category/package1
category/package2
category/package3
category/package4
[...]
category/packageN"

CFLAGS="-option1 -option4 -option4"
PACKAGES="category/packageN+1
category/packageN+2
category/packageN+3
category/packageN+4
[...]
category/packageN+M"

LINGUAS="pl"
PACKAGES="category/package3
category/package5"

and so on. 
there is one disadvantage in this idea. it's pretty certain, that man
want to have diffrent CFLAGS and CXXFLAGS for the same package. in
contruction as above, he'd have to copy packages and have the same
package in 2 places, so i think, we could set these flags together, for
example:

CFLAGS="..."
CXXFLAGS="..."
PACKAGES="..."

CFLAGS="..."
PACKAGES="..." <no CXXFLAGS definition here -> CXXFLAGS are taken from make.conf

now one can say: "hey - why the hell CFLAGS and CXXFLAGS are treated in
diffrent way than the rest?". ok. so let's make:

CFLAGS="..."
CXXFLAGS="..."
MAKEOPTS="..."
PACKAGES="..."

CFLAGS="..."
PACKAGES="..." < again - not declared setting are taken from enviroment here

isn't that clear anought? let's make /etc/portage/package.env a
directory.

ls /etc/portage/package.env
set1.env
set2.env
set3.env

cat /etc/portage/package.env/set1.env
# definitions for base-system
CFLAGS="..."
CXXFLAGS="..."
MAKEOPTS="..."
PACKAGES="..."

cat /etc/portage/package.env/set2.env
# definitions for kde
CFLAGS="..."
LINGUAS="..."
PACKAGES="..."

and so on...
what do you think of that?

-- 
"Life's a bitch and so am I, the world owes me, so fuck you." - Green Day
PoLiSh YoUr EnGlIsH:
 KIOSK RUCHU - LITTLE BUSINESS OF MOVEMENT 
  

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-09-01 14:02 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 [this message]
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=20040901140246.GA5942@CogES \
    --to=aye@gentoo.pl \
    --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