From owner-freebsd-current@FreeBSD.ORG Wed May 28 02:14:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E64F537B401 for ; Wed, 28 May 2003 02:14:29 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 104C043FB1 for ; Wed, 28 May 2003 02:14:29 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4S9EPkA061183; Wed, 28 May 2003 03:14:25 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 28 May 2003 03:14:03 -0600 (MDT) Message-Id: <20030528.031403.32720860.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200305281524.10145.doconnor@gsoft.com.au> References: <200305281147.53271.doconnor@gsoft.com.au> <20030527.225207.101586684.imp@bsdimp.com> <200305281524.10145.doconnor@gsoft.com.au> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 09:14:30 -0000 In message: <200305281524.10145.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : You need 'FORCE_PKG_REGISTER=' in the install target. True. : 1) If the port is updated between builds you end up with two version of the : port installed. True. That's a weakness in the ports system, which is why we have portupgrade. However, I didn't want to require portupgrade for something so 'simple'. : 2) You can't control where the module gets put - arguably this isn't a : calamity, but I think it makes more sense for the modules to end up in : /boot/modules, or some analog to it that is in $PREFIX. It should go in /boot/kernel, and not into $PREFIX, but that's a philisophical problem I have with ports. ALL modules should be in /, imho, since you don't know if the module is required to mount /. : I guess the problem with mandating somewhere in $PREFIX is that the loader : can't load it, so that's no good. I guess the only choice left is : /boot/modules. /boot/kernel : Any comments? Well, the patch was mostly a strawman to promote discussions about the issues. Warner