Date: Wed, 28 May 2003 07:28:37 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? Message-ID: <20030528142837.GA30174@troutmask.apl.washington.edu> In-Reply-To: <200305281840.46645.doconnor@gsoft.com.au> References: <200305281350.27953.doconnor@gsoft.com.au> <200305281447.02322.doconnor@gsoft.com.au> <20030528.030900.55833611.imp@bsdimp.com> <200305281840.46645.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 28, 2003 at 06:40:46PM +0930, Daniel O'Connor wrote: > On Wed, 28 May 2003 18:39, M. Warner Losh wrote: > > : > : Maybe the kernel build stuff can look in /usr/local/src/sys/modules > > : > : for things to build or something.. > > : > > > : > YUCK! > > : > > : *WHY?* > > : > > : I have asked this before BTW, and I haven't been told why it sucks. > > > > Because there are other, more elegant ways of dealing with these > > things. I don't like /usr/local/src anything, which was the main > > complaint. > > If there are more elegant solutions I would like to know what they are. > > I agree it isn't a great solution, but I can't see what is better. > For GPL modules, put them in src/sys/gnu. If you don't want bloat, then use cvsup and a refuse file to not retrieve the sys/gnu. See the discussion that occurred many years ago when maestro3 support was committed to the tree. For non-viral licensed code, put it in its proper place in the sys/ hierarchy. Then use a WANT_XXX=yes knob in the /etc/make.conf to cause XXX to be built. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030528142837.GA30174>