Re: [PATCH] Remove framework for external modules

[Robert Millan <rmh@aybabtu.com>]

On Fri, Aug 28, 2009 at 04:04:39PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >> (footnote) We are applying GPL license to these modules, but they'll
> >> never end up in the grub tree. Our requirements are too weird. You
> >> won't want to merge this code, believe me.
> >
> > I understand.  Good luck with it!
> This case is exactly something external module build want to prevent.
> If it wasn't available people wanting weird thing would be likely to
> end up with a badly maintained unsynced own fork. In turn this fork is
> likely to cause repeat of old bug reports on savannah. (I know posting
> fork bugs to savannah isn't appropriate but we have inapropriate bug
> reports even now (e.g. bugs in debian build system))

This is not a fork.  Private modifications are very common in the free
software world, specially in corporate environments which tend to have
very specific requisites.

The only question is whether we should take extra steps to make these
modifications easier.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."