Gentoo Archives: gentoo-portage-dev

From: "Kevin F. Quinn" <kevquinn@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [Bug 44796] Per package environment variables
Date: Fri, 04 Nov 2005 10:04:47
Message-Id: SW2H6P.1811450929XJC8C@gentoo.org
In Reply to: Re: [gentoo-portage-dev] [Bug 44796] Per package environment variables by Brian Harring
1 On 3/11/2005 13:45:16, Brian Harring (ferringb@g.o) wrote:
2
3 > Offhand, why isn't this a bashrc trick?
4
5 I took a cue from solar's autopatch bashrc stuff, and wrote the attached.
6 Sources whatever it finds in a sort of shell-file overlay that matches the
7 package being built and optionally the current ebuild phase, so you create
8 a sort of per-package (and per-phase) additional bashrc.
9
10 One thing it can't do is affect the environment for the fetch phase (where
11 bashrc is not sourced). Unfortunately, this is what I originally wrote it
12 for; I wanted to have a specific value of LINGUAS for a the Acrobat reader
13 package (see bug #97401).
14
15 I'd guess that a package.env supported from portage itself wouldn't have
16 this restriction.
17
18 Kev.

Attachments

File name MIME type
bashrc.packagesh application/x-not-recognised