Date: Thu, 2 Mar 1995 23:49:50 -0800 From: "Jordan K. Hubbard" <jkh@FreeBSD.org> To: ports@freefall.cdrom.com Subject: Ok, I'm stumped. Message-ID: <199503030749.XAA02499@time.cdrom.com>
next in thread | raw e-mail | index | archive | help
You know the problem - some stupid port keeps blowing up while you're trying
to verify a build from the top and it's driving you nuts. Sure, you can
take it out of the Makefile but what you'd *really* like to do is just
skip over it after you've verified that it doesn't work for the duration
of your build session. You don't want to have to modify Makefiles to
disable it if you can possibly avoid it.
To this end, I set out to try and create a "NO_<portname>" variable that
would cause the port to be skipped in the same way that IS_INTERACTIVE
ports are switched off when BATCH is set.
The problem is that I'm kinda stumped on how to do it. Setting a variable
called NO_foobar to disable the foobar port is all well and good, but
we've got no variable anywhere that defines a port as simply "foobar"! :-(
We've got ${DISTNAME} but that's unfortunately often set to things like
foobar_11b-20.1 which doesn't make a good shell variable name. Or we've
got ${.CURDIR}, but that's set to /usr/ports/blah/bar/foobar. Sigh.
What would be neat would be some way of picking off the `entry' in
bsd.port.subdir.mk and checking to see if the value of "X${NO_$${ENTRY}}" = "X",
but I don't see any easy way of doing the recursive shell variable expansion.
Any suggestions? This is where my knowledge of `sh' leaves off! :-(
Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503030749.XAA02499>