Re: Bug#353277: ndiswrapper in main

[Ian Jackson <ian@davenant.greenend.org.uk>]

Manoj Srivastava writes ("Re: Bug#353277: ndiswrapper in main"):
>         Well, yes. Consider the case that I write up a compiler for a
>  new language in C++ or ruby.  Can I put this compiler in main? Even
>  if there is no public repository of code in this new language?

These arguments seemed entirely mystifying to me until I figured out
what Manoj is trying to do.

Manoj, you're trying to establish or find a rule which depends only on
the direction of dependency interrelationships and formal copyright
status, and other things that can be clearly determined without regard
to actual existence of any software, usual or plausible use cases, and
intents of packagers and users.  Am I right ?

I think this is a mistake.  It's obvious what the real difference is
between these situations.  A compiler is frequently used for learning
about the language, for writing and running programs locally, and
other such things.  While these are possible uses for ndiswrapper
no-one is seriously suggesting that they are _sensible_ uses for
ndiswrapper.

You wouldn't use ndiswrapper to learn about the NDIS interface, even
though that's theoretically possible, and you wouldn't use it for
developing and running network drivers locally.  The reasons for this
are contextual and in many respects in principle subjective - but
no-one is disputing these facts.

Just because an interpretation or a principle requires us to make a
subjective value judgement, or look at the intent behind something, or
look at the surrounding ecology of software, doesn't mean that it's a
bad principle.  After all, trying to make the best judgement when the
situation is subjective and/or unclear is bread and butter for
programmers !

>         The only argument I have seen so far seems to imply that I
>  can't package up new emulators  or compilers unless I also provide
>  free source code for these to process, I am not sure I think that
>  expands freedom in any tangible manner.

You can package up new emulators or compilers if it's reasonable to
suppose that the user might install it _to run home-grown `content'_.

Ian.