Re: [gentoo-dev] Common make.conf screwups?

[Drake Wyrm <wyrm@haell.com>]

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

At 2004-11-19T14:42:37+0000, Brian Jackson <iggy@gentoo.org> wrote:
> On 7:45:29 pm 11/18/04 Ciaran McCreesh <ciaranm@gentoo.org> wrote:
> > I've got some better vim syntax highlighting rules for make.conf lined
> > up to go into the next app-vim/gentoo-syntax. One of the things that
> > this lets me do is highlighting of (some kinds of) mistakes. What're
> > the most common screwups that people see? My current list is:
> 
> I don't know if you can detect it, but basing a var on another unset var,
> i.e.
> 
> #PORTDIR=/usr/portage
> then later in make.conf:
> PKGDIR=${PORTDIR}/packages
> or something similar

I understand what you're thinking, but that's a bad example... $PORTDIR
is set to its default of "/usr/portage" before make.conf is parsed. Your
example would set $PKGDIR to "/usr/portage/packages" anyway. An
interesting quirk is found when one changes $PORTDIR without uncommenting
all the variables which use it. For example:

PORTDIR=/some/where/else
#PKGDIR=${PORTDIR}/packages

in one's make.conf leaves $PKGDIR set to "/usr/portage/packages".

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]