From owner-cvs-etc  Wed Jun  4 16:22:33 1997
Return-Path: <owner-cvs-etc>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA00390
          for cvs-etc-outgoing; Wed, 4 Jun 1997 16:22:33 -0700 (PDT)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00382;
          Wed, 4 Jun 1997 16:22:27 -0700 (PDT)
Received: from labs.usn.blaze.net.au (local [127.0.0.1])
	by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id JAA16970;
	Thu, 5 Jun 1997 09:22:21 +1000 (EST)
Message-Id: <199706042322.JAA16970@labs.usn.blaze.net.au>
X-Mailer: exmh version 2.0gamma 1/27/96
To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>
cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-etc@FreeBSD.ORG
Subject: Re: cvs commit: src/etc/mtree BSD.include.dist 
In-reply-to: Your message of "Thu, 05 Jun 1997 03:08:45 +0400."
             <Pine.BSF.3.96.970605030604.3289A-100000@lsd.relcom.eu.net> 
X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P<Wc^}f75I|456ez/M
 E3OlD+ZL@c>#N+Ec~Z&@;'LL!;3?y<m[SK`'\R~Oe|(t-x+U@a%p!1_fZP0!Tb^?'%M1|"n9
 Fl{Ao~%X[Ec|bMlaN-3#x.e')nZ2/HHYSa2D[:bk#pj0(}\HpKeE}/GqUb3-1}lnUm6Et4?(
 gB5[*Z3Mu6o{Og.EJ))beY9oq9wcVU7_n}:I2JvCaa[5=&PI;x__["DL`uI}=s>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Jun 1997 09:22:20 +1000
From: David Nugent <davidn@labs.usn.blaze.net.au>
Sender: owner-cvs-etc@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > I guess so, unless we mandate the source dist.  You know where the
> > symlinks are pointing at, right?
>  
> What bad happen in keeping the same scheme for release and for source
> distribution and avoid such special cases?
> I see some troubles happens if somebody will try to extract source
> distribution over release (symlinks which overwrites directories)

No, the symlinks go the other way (from /usr into /usr/src), and since
all of the source distribution is in /usr/src, there's no danger in
overwriting when extracting the source distribution. make world which
includes make includes clobbers the directories in /usr/include and
(re)makes the symlinks, kernel builds don't use /usr/include anyway,
so there's no problem there either.

I believe mtree being able to selectively not follow symlinks would be
a possible solution here.


Regards,
David

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/