Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jun 1997 16:19:02 -0700 (PDT)
From:      asami@cs.berkeley.edu (Satoshi Asami)
To:        ache@nagual.pp.ru
Cc:        bde@zeta.org.au, cvs-all@freebsd.org, cvs-committers@freebsd.org, cvs-etc@freebsd.org
Subject:   Re: cvs commit: src/etc/mtree BSD.include.dist
Message-ID:  <199706042319.QAA01463@vader.cs.berkeley.edu>
In-Reply-To: <Pine.BSF.3.96.970605030604.3289A-100000@lsd.relcom.eu.net> (message from =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= on Thu, 5 Jun 1997 03:08:45 %2B0400 (MSD))

next in thread | previous in thread | raw e-mail | index | archive | help
 * What bad happen in keeping the same scheme for release and for source
 * distribution and avoid such special cases?

So are you suggesting that we make users install the source
distribution just because they want to compile something?  Or are you
saying we do it the other way, having them always as directories?

 * I see some troubles happens if somebody will try to extract source
 * distribution over release (symlinks which overwrites directories)

I think you got this backwards. ;)  If you extract a source
distribution, it will all go under /usr/src.  The /usr/include/* will
stay as directories.

Only when you do a make world (or say the magic words in
/usr/src/include), the directories in /usr/include will be replaced
with symlinks to the source dist.

 * What about deeper level directories I ask?

All I said was that there doesn't appear to be any directories not
specified in BSD.include.dist (it was an answer to your question to
Peter about if there is anything special for the release).  Are there
any other directories needed under /usr/include for compilation of
userland code?

Satoshi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706042319.QAA01463>