From owner-freebsd-bugs  Thu Sep 19 01:34:51 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA17273
          for bugs-outgoing; Thu, 19 Sep 1996 01:34:51 -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 BAA17243;
          Thu, 19 Sep 1996 01:34:43 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id BAA13646; Thu, 19 Sep 1996 01:34:41 -0700 (PDT)
To: Jason Thorpe <thorpej@nas.nasa.gov>
cc: Julian Elischer <julian@current1.whistle.com>,
        GNATS Management <gnats@freefall.freebsd.org>,
        freebsd-bugs@freefall.freebsd.org
Subject: Re: bin/1643: Support for NetBSD in bsd.port.mk 
In-reply-to: Your message of "Wed, 18 Sep 1996 22:58:45 PDT."
             <199609190558.WAA27939@lestat.nas.nasa.gov> 
Date: Thu, 19 Sep 1996 01:34:41 -0700
Message-ID: <13644.843122081@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Well, kinda hoping for a unified "ports" collection (_I_ certainly prefer 
> the name "opt", as do the NetBSD folks I've asked so far... :-)

I'm not sure I do.  /opt and /usr/opt have very definite Sun-ish
connotations for me, given that Sun was the first I knew to use that
organizational hierarchy, and they used it for something rather
different than /usr/ports (similar, but still different).  Hence, I
always preferred to just avoid any potential confusion by giving the
ports collection its own place to live.  I considered but rejected
/opt and /usr/opt as candidates when I first wrote that file.

					Jordan