Date: Sat, 22 Jun 1996 12:15:01 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Wolfram Schneider <wosch@cs.tu-berlin.de> Cc: current@freebsd.org Subject: Re: Wanted: Testers for an alternate to /usr/obj (as we know it). Message-ID: <1485.835470901@time.cdrom.com> In-Reply-To: Your message of "Sat, 22 Jun 1996 20:27:38 %2B0200." <199606221827.UAA06752@campa.panke.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> It allow multiple 'make all', I thought this was the main goal.
It was the main one, yes, but not the only one. I did check into
BSDOBJDIR when I first started this, believe me, but it simply wasn't
as seamless a mechanism as I liked - I wanted the user to be able to
do a `make world' straight from a CD, too, and without having to know
any special magic.
> 1. I think this confuse many people, I expect many 'where are
> the object files?' questions in the future.
I'll document it.. :-)
Also, there's the OBJLINK feature I just added which *could* be
enabled by default during the transition period, I guess. We'd just
have to tell the CD people to turn it off. I dunno, it seems a lot
more elegant to leave it off! :-)
> 2. We have mount_unions. If it is broken, fix it (remember the
> NFS discussion - we don't change the system if a minor part
> is wrong)
mount unions aren't going to work anywhere soon enough to do me any
good, sorry (unless you intend to fix them :-).
> 3. A read-only /usr/src is a feature, it should not
> break the current algorithm with obj symlinks
I would argue that a read-only src is BLOODY MANDATORY and people who
start stomping on that concept are likely the same silly people who
write on string constants in C and need to have all their code
compiled with -fwritable-strings! :-) However, I'm not so militant
about it that I'd make it an unchangable policy and that's why I gave
Nate his OBJLINK feature.
Sorry, but there are so many more reasons to argue for a read-only
/usr/src than not that I think it's something of a specious argument.
> 4. Don't change the behavior of MAKEOBJDIR, use a new variable
> (e.g. MAKEOBJROOTDIR) and set .OBJDIR internally to
> $MAKEOBJROOTDIR/${.CURDIR}/$MAKEOBJDIR or $MAKEOBJROOTDIR/${.CURDIR}
See my mail to Bruce. I will if someone can give me a good reason for
adding another variable to replace one which was ill-conceived in the
first place (it used to contain the value "obj" for godsakes - how
much more useless can you get?). Truly, has anyone out there ever
used MAKEOBJDIR in something _other_ than the BSD src tree?
Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1485.835470901>