From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14407 invoked from network); 1 Sep 2004 14:02:52 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 1 Sep 2004 14:02:52 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1C2VhL-0006pS-Ez for arch-gentoo-dev@lists.gentoo.org; Wed, 01 Sep 2004 14:02:51 +0000 Received: (qmail 22035 invoked by uid 89); 1 Sep 2004 14:02:50 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 13016 invoked from network); 1 Sep 2004 14:02:48 +0000 Date: Wed, 1 Sep 2004 16:02:46 +0200 From: aye To: gentoo-dev@lists.gentoo.org Message-ID: <20040901140246.GA5942@CogES> References: <4134FB0B.9060501@ifm.liu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <4134FB0B.9060501@ifm.liu.se> User-Agent: Mutt/1.5.6i Subject: Re: [gentoo-dev] per-package environment variables. X-Archives-Salt: 002ddec3-d115-47f4-9ec0-90b007a2ffa7 X-Archives-Hash: a105a0746409fa9a7db3de1d2e19bae2 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="..." 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