Rafael Laboissiere wrote:
>
> L. And this means that we _must_ ship the source used for building it.
>>
>> I wrote a lot of the code in the comms toolbox (the majority in terms of
>> line count), and wrote the documentation. I suppose except for a couple
>> of
>> corner cases, I can give permission to distribute the pdf without the
>> source
>> texinfo files.. In any case what you are saying means that no one can
>> distribute the documentation without the source code either, this seems
>> rather a strange situation to me.
>
> The situation is not clear. I will ask in debian-legal about this.
>
Another example is the Octave manual itself that you can buy a copy of. A
large part of the text is straight from the help strings of the code... I
suppose then that the book should be delivered with the source code.
D.
--
View this message in context:
http://www.nabble.com/Documentation-for-communications-package-tp16525834p16531083.html
Sent from the octave-dev mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
