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

Re: more evil firmwares found



William Ballard wrote:

> On Sun, Apr 25, 2004 at 12:37:13AM -0500, Ryan Underwood wrote:
>> obvious division between a program and its supporting materials.  My
>> claim is that only through a massive logical leap can we declare the
>> supporting materials to fall under the definition of "program" as well.
>> This leap is what is required to remove a freely licensed albeit
>> indeterminate binary-blob from Debian on a DFSG basis.
> 
> I have a program, http://sourceforge.net/projects/pim-tb, under GPL.
> My "preferred form" for working with it is a file called proj.c and a
> set of .c and .xml files, in a flat structure.  I compile proj.c to
> a.out; run ./a.out to produce "proj" bash script, and './proj' creates
> the directory structure, generates Makefile.ac, and makes it a "normal
> project."
> 
> In particular the "master copy" of the changelog and Readme (a document)
> is stored on proj.c.  The first time I distributed the project as proj.c
> and a bunch of files in a flat file, people didn't know what the hell to
> do with it.  So I started distributing the resulting output, ready to
> ./configure and make.
> 
> Clearly, the output is the "preferred form."
...for compilation.  Not necessarily for modification.

>  However, *I* make the
> master changes to the project in proj.c, blow away the output, and
> distribute the "generated project."
> 
> Am I required to distribute proj.c?  Clearly no one else *wants* it.
I think you are.

Please do so anyway; it sounds interesting.  You should still distribute the
generated output, of course; just *also* make proj.c & company available,
and mention that you use it as source.

-- 
There are none so blind as those who will not see.



Reply to: