Re: policy on GPL'd drivers?

If we are talking about something like a network interface that needs to
be preloaded, then I would be inclined to see a port install the module
into /usr/local/modules (which is what 'rtc' uses) and have a
pkg-install message that states the need to do a 
'cp /usr/local/modules/if_??.ko /boot/kernel' 
and add 'if_??_load="YES"' to loader.conf so the network interface can
be initialised on boot.

This way the port isn't installing anything outside $PREFIX, and isn't
directly altering /boot/loader.conf.

Seeya...Q

On Wed, 2003-05-28 at 15:54, Daniel O'Connor wrote:
> On Wed, 28 May 2003 14:22, M. Warner Losh wrote:
> > In message: <200305281147.53271.doconnor_at_gsoft.com.au>
> >
> >             "Daniel O'Connor" <doconnor_at_gsoft.com.au> writes:
> > : The only downside is that there are no hooks into the build process so
> > : you have to be VERY careful when you update your kernel, or you get
> > : panics :(
> >
> > This is true.  I'd thought that MODULES_OVERRIDE would help, but ports
> > builds and kernel builds are different enough to make this not easy to
> > do.
> >
> > Wanna test a patch?  Add a 'makeoptions PORTS_MODULES=comms/ltmdm' to
> > your config file and apply the following patch.  Lemme know how well
> > (or poorly) it works.  There's likely some hidden assumptions that
> > make it appear to work for me.
> 
> I don't see how it can work properly..
> 
> You need 'FORCE_PKG_REGISTER=' in the install target.
> 
> I don't think how the patch is structured is sensible though :)
> 
> 1) If the port is updated between builds you end up with two version of the 
> port installed.
> 
> 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.
> 
> IMHO a standard should be set WRT item 2 so future ports writers know what the 
> proper way to do it is :)
> 
> 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.
> 
> Any comments?