policy on GPL'd drivers?

[Daniel O'Connor]

On Wed, 28 May 2003 23:58, Steve Kargl wrote:
> > > 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.

You are describing how it happens now, not WHY it happens like that.

I think the existing solution has problems, and would prefer some external 
hooks for 3rd party modules.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140  AE4B 319B 41F4 5D17 FDD5