From owner-freebsd-current  Tue Sep 24 12:19:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id MAA18776
          for current-outgoing; Tue, 24 Sep 1996 12:19:38 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA18768
          for <current@FreeBSD.org>; Tue, 24 Sep 1996 12:19:35 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id MAA07271; Tue, 24 Sep 1996 12:13:15 -0700 (PDT)
To: Warner Losh <imp@village.org>
cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.org
Subject: Re: install on {Net,Open}BSD vs install on FreeBSD 
In-reply-to: Your message of "Tue, 24 Sep 1996 08:41:51 MDT."
             <199609241441.IAA05913@rover.village.org> 
Date: Tue, 24 Sep 1996 12:13:15 -0700
Message-ID: <7269.843592395@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> I'd still like to merge in the -d code from NetBSD/OpenBSD.  SunOS
> also sets the precident.  While it is true the permissions aren't
> exactly right, other software than FreeBSD's 'make install' uses this
> to make sure directories are present.  This other software does happen

I tend to agree.  The mtree files represent an "idealized" view of the
permission hierarchy and are certainly preferable to all else in
creating an installation which has all directories created with the
appropriate permissions, but in practice it's not practical to run the
mtree files every time you want to install some random port which is
going to want to create new directories under /usr/local, /usr/X11R6
or some other central location.

I'd say implement -d also, but discourage its use in the ports collection.

					Jordan