From owner-freebsd-current Sun Aug 3 19:43:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA06576 for current-outgoing; Sun, 3 Aug 1997 19:43:20 -0700 (PDT) Received: from pcpsj.pfcs.com (pVNzOh0SXA8p7UuhrrcUcoa0jgm6xLxM@harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06564 for ; Sun, 3 Aug 1997 19:43:12 -0700 (PDT) Received: from mumps.pfcs.com (mumps.pfcs.com [192.52.69.11]) by pcpsj.pfcs.com (8.8.6/8.6.9) with SMTP id WAA01783 for ; Sun, 3 Aug 1997 22:43:04 -0400 (EDT) Received: from localhost by mumps.pfcs.com with SMTP id AA08990 (5.67b/IDA-1.5 for ); Sun, 3 Aug 1997 22:43:03 -0400 To: current@FreeBSD.ORG Subject: Re: Current is currently really a mess (was: Re: Tk/Tcl broken(?)) In-Reply-To: jkh@time.cdrom.com's message of "Sun, 03 Aug 1997 16:10:23 PDT." <4492.870649823@time.cdrom.com> Date: Sun, 03 Aug 1997 22:43:01 -0300 Message-Id: <8988.870662581@mumps.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Here are a couple possible solutions to the situation with ports. First, go from the current paradigm to one that is more tightly based on an autoconf/metaconfig basis. I figure this is a lousy idea, and is probably unworkable. Second, "enhance" the ports paradigm to support multiple versions of FreeBSD. That way, each port can have FreeBSD-version-specific Makefile and patches. With this scheme, a single copy of the ports tree could be used to build/debug on a variety of versions of FreeBSD. I'm suggesting these ideas bacause it's been my experience that *I* prefer {sup,}porting a tree that looks like: package1/target1 package1/target2 package2/target1 package2/target2 ... as opposed to: target1/package1 target1/package2 ... target2/package1 target2/package2 ... especially when there are more packages than targets. H