[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#353277: ndiswrapper in main

This one time, at band camp, Hamish Moffatt said:
> On Tue, Feb 28, 2006 at 10:31:17AM +0000, Stephen Gran wrote:
> > This one time, at band camp, Hamish Moffatt said:
> > > flashplugin-nonfree itself contains scripts which I presume meet the
> > > DFSG. Do you think we should put it in main?
> > 
> > I assume this is a troll, and you have not bothered to read any of the
> > other messages in this tediously long thread.  
> It's not a troll. In the quote that you trimmed, you said that all
> dependencies are expressed as Depends: in the control file. I explained
> why this is not the case. Please acknowledge that you understand this.

Of course I understand this.  In another post I explained that examples
of packages that should be in contrib are things like installers for
non-free software.  Since flashplugin-nonfree is exactly one of these, I
have to assume you didn't read the rest of the thread, and were just
trolling.  Sorry if you just missed it under all the noise.

Since ndiswrapper is not an installer for non-free software, I don't
actually see what flashplugin-nonfree hass to do with the discussion.

> > > > ndiswrapper is a piece of free software.  It does not need non-free tools
> > > > to build, and it will execute as a standalone app without any drivers.
> > > 
> > > (And do what? Display a usage screen? Anything more?)
> > 
> > This has already been answered.  Please feel free to read the archives.
> I have read the whole thread, and it hasn't been answered adequately.
> Your argument is simply that an unuseful driver is enough reason to
> put ndiswrapper in main. You argue that contrib is not enough because
> then it won't be available in the installer. This must mean that it's
> needed at install time to use non-free drivers.

No, this was someone else's argument.  My argument is that ndiswrapper
successfully enables a kernel API to allow drivers that use an NDIS
stack to communicate with the linux network stack.  It does this,
whether or not those drivers are ever used.  Non-free drivers need
ndiswrapper to execute on linux.  ndiswrapper does not need non-free
drivers.  Does that make my position clear enough?
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |

Attachment: signature.asc
Description: Digital signature

Reply to: