Date: Wed, 28 May 2003 03:14:03 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: doconnor@gsoft.com.au Cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? Message-ID: <20030528.031403.32720860.imp@bsdimp.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200305281524.10145.doconnor@gsoft.com.au>
"Daniel O'Connor" <doconnor@gsoft.com.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030528.031403.32720860.imp>