Re: LCC and blobs
Josselin Mouette <firstname.lastname@example.org> writes:
> Le samedi 11 décembre 2004 à 21:47 +0000, Matthew Garrett a écrit :
>> Goswin von Brederlow <email@example.com> wrote:
>> > With drivers that load external firmware files this split is possible
>> > leaving the driver in main inside the kernel and the non DFSG free
>> > firmware in non-free.
>> This argument suggests that we can shift drivers from contrib to main
>> simply by turning them into kernel patches and getting them included in
>> the stock kernel. This seems, uh, odd.
> Odd, but that's how it should be.
>> We put it in contrib
>> so that people know that by using this software, they will also have to
>> use non-free code. This is less obvious for drivers that use firmware in
>> flash, but it's still true.
> Where do you put xine, then? It works fine with only free code, but can
> open more formats when dlopen()ing optional non-free libraries. Should
Optional is the key work imho. If the software works fine without it
then it is optional and just a suggests. No need for contrib.
You don't have to taint it but you can.
> it go outside of main because it is "tainted"? I don't believe so; the
> user himself chooses to taint his system by installing these libraries.
> The problem is exactly the same for non-free blobs: the user will know
> he is installing some non-free stuff, either by downloading it from our
> non-free archive, either by installing it by himself.
> .''`. Josselin Mouette /\./\
> : :' : firstname.lastname@example.org
> `. `' email@example.com
> `- Debian GNU/Linux -- The power of freedom