1 |
At 2004-11-19T14:42:37+0000, Brian Jackson <iggy@g.o> wrote: |
2 |
> > I don't know if you can detect it, but basing a var on another unset var, |
3 |
> > i.e. |
4 |
> > |
5 |
> > #PORTDIR=/usr/portage |
6 |
> > then later in make.conf: |
7 |
> > PKGDIR=${PORTDIR}/packages |
8 |
> > or something similar |
9 |
|
10 |
On Saturday 20 November 2004 07:00, Drake Wyrm wrote: |
11 |
> I understand what you're thinking, but that's a bad example... $PORTDIR |
12 |
> is set to its default of "/usr/portage" before make.conf is parsed. |
13 |
|
14 |
It is set, but the "defaults" are not taken into account when make.conf is |
15 |
parsed. Each file is its own entity. |
16 |
|
17 |
> Your example would set $PKGDIR to "/usr/portage/packages" anyway. |
18 |
|
19 |
# cat /etc/make.globals |egrep "^(PORTDIR|PKGDIR)" |
20 |
PORTDIR=/usr/portage |
21 |
PKGDIR=${PORTDIR}/packages |
22 |
# cat /etc/make.conf |egrep "^(PORTDIR|PKGDIR)" |
23 |
PKGDIR="${PORTDIR}/packages" |
24 |
# emerge info |egrep "^(PORTDIR|PKGDIR)" |
25 |
PKGDIR="/packages" |
26 |
PORTDIR="/usr/portage" |
27 |
PORTDIR_OVERLAY="" |
28 |
|
29 |
> An interesting quirk is found when one changes $PORTDIR without uncommenting |
30 |
> all the variables which use it. For example: |
31 |
> |
32 |
> PORTDIR=/some/where/else |
33 |
> #PKGDIR=${PORTDIR}/packages |
34 |
> |
35 |
> in one's make.conf leaves $PKGDIR set to "/usr/portage/packages". |
36 |
|
37 |
This is correct. |
38 |
|
39 |
Regards, |
40 |
Jason Stubbs |
41 |
|
42 |
-- |
43 |
gentoo-dev@g.o mailing list |