From owner-freebsd-ports Sat Aug 2 16:29:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA21560 for ports-outgoing; Sat, 2 Aug 1997 16:29:24 -0700 (PDT) Received: from trefoil.bogs.org (root@bogslab.ucdavis.edu [128.120.162.26]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA21555 for ; Sat, 2 Aug 1997 16:29:21 -0700 (PDT) Received: from myrtle.bogs.org (root@myrtle.bogs.org [198.137.203.39]) by trefoil.bogs.org (8.7.4/8.7.3) with SMTP id QAA07687 for ; Sat, 2 Aug 1997 16:29:17 -0700 (PDT) Received: from myrtle.bogs.org (greg@localhost [127.0.0.1]) by myrtle.bogs.org (8.6.12/8.6.12) with ESMTP id QAA00230 for ; Sat, 2 Aug 1997 16:29:12 -0700 Message-Id: <199708022329.QAA00230@myrtle.bogs.org> To: ports@freebsd.org Subject: /usr/ports ?? Reply-To: gkshenaut@ucdavis.edu Date: Sat, 02 Aug 1997 16:29:06 -0700 From: Greg Shenaut Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Regarding the perl and tk/tcl ports debate-- perhaps I'm being naive here, but would it help to have all (and only) ports installed under /usr/ports? This would be somewhat similar to /usr/contrib in certain other systems. All "standard" ports would go into /usr/ports; other add-ins would go in /usr/local; anything needed for the base system would go elsewhere. The ports team would be responsible only for the stuff under /usr/ports. Symbolic links (such as /usr/bin/perl5 --> /usr/ports/bin/perl5.4321) would give the user more flexibility. -Greg