1 |
On Thu, 2006-06-08 at 06:49 -0400, Alec Warner wrote: |
2 |
> Mike Frysinger wrote: |
3 |
> > On Wednesday 07 June 2006 19:12, Alec Warner wrote: |
4 |
> > |
5 |
> >>I would be more concerned with convincing the rest of the developers. |
6 |
> >>adding crap in base profile.bashrc will affect 99% of users, so it |
7 |
> >>better be friggin correct and useful, otherwise you will piss a ton of |
8 |
> >>people off. |
9 |
> > |
10 |
> > |
11 |
> > versus the people who are really annoyed that such support hasnt yet been |
12 |
> > integrated into portage proper ? |
13 |
> > |
14 |
> > yes, from the portage side of things, it may be a pita to implement |
15 |
> > per-package env ... but from the user side of things, it's a huge help |
16 |
> > -mike |
17 |
> |
18 |
> My e-mail was basically worded as to say "Solar paste your crap to this |
19 |
> ML." |
20 |
|
21 |
Alright... |
22 |
|
23 |
tail -n 6 /usr/portage/profiles/uclibc/profile.bashrc |
24 |
|
25 |
#for conf in ${PN}-${PV}-${PR} ${PN}-${PV} ${PN}; do |
26 |
# if [[ -r /etc/portage/env/$CATEGORY/${conf} ]]; then |
27 |
# . /etc/portage/env/$CATEGORY/${conf} |
28 |
# break |
29 |
# fi |
30 |
#done |
31 |
|
32 |
> Is there any reason you need package.env in portage proper as |
33 |
> opposed to bashrc? |
34 |
|
35 |
Nope.. bashrc is the only way to access the variables in a way that |
36 |
is the most friendly to the bash side of things. |
37 |
|
38 |
-- |
39 |
Ned Ludd <solar@g.o> |
40 |
Gentoo Linux |
41 |
|
42 |
-- |
43 |
gentoo-dev@g.o mailing list |