From owner-freebsd-ports Fri Sep 8 19:48:26 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 4E51C37B505; Fri, 8 Sep 2000 19:48:23 -0700 (PDT) Received: from silvia.hip.berkeley.edu (sji-ca14-01.ix.netcom.com [205.186.215.1]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA10111; Fri, 8 Sep 2000 22:47:59 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.11.0/8.11.0) id e892lUN06573; Fri, 8 Sep 2000 19:47:30 -0700 (PDT) (envelope-from asami) To: Will Andrews Cc: Kris Kennaway , FreeBSD Ports Subject: Re: Ports Options Paper References: <20000908211201.C632@radon.gryphonsoft.com> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 08 Sep 2000 19:47:00 -0700 In-Reply-To: Will Andrews's message of "Fri, 8 Sep 2000 21:12:01 -0500" Message-ID: Lines: 42 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Will Andrews * On Fri, Sep 08, 2000 at 06:52:53PM -0700, Satoshi - Ports Wraith - Asami wrote: * > * This has been implemented by NetBSD already. * > * > Let's take it from them then. * * *sigh* fine.. someone can figure out how different their code is * and how to merge it.. real great idea.. and then what if their * implementation is limited by their own system? Or if there's a better * way to do it? What are you trying to say? * Except that you can change the target on the command line, and it won't * make a difference which directory you're in. The solution for clashing You can do pretty much the same thing with the current system too. If you want to move more stuff into master ports (such as extra pkg files, etc.) and leave only the Makefile in the slave ports, that will be exactly like what you say here. People can go to the master and select the option or use one of the slaves which have some options pre-selected for them. * It's not really related to ports-options. However, it is an issue that * I'm not happy with. I'm tired of having versioned port directories just * because our Makefile and CVS systems can't handle it otherwise. In my * utopia system, both kde meta-ports would rest in x11/kde and you would * specify the version you wanted that way; this would also apply to the * various split-up ports around the tree. What does CVS have to do with it? At any rate, I actually happen to like the fact that currently, a port can say "I depend on X libraries" by setting a dependency on XFree86-4-libraries. (Ok, so it is really buried in USE_* stuff, but that's not the point.) This leaves nothing unambiguous and makes ports easy to understand/write/maintain. I don't see anything wrong with that. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message