>From: Manuel Clos <[EMAIL PROTECTED]>


>I didn't know that it was unrelated stuff, I just looked into all the 
>files searching for license statements.

These sources that create e.g. the CRC tables are unneeded even in a souce 
distrbution. You only need it if you like to modify the code to make it
fit to other applications that use different CRC polynoms...

>>>I don't know where this libedc_ecc come from, since I was unable to find 
>>>a web page or tarball anywhere.
>> 
>> It has been removed because cdrdao abuses it :-(
>> 

>Ok, let's fix it then.

Well a few days did pass and nothing did happen. Why?

>> Read the Copyright information inside cdrtools. Cdrtools use the package 
>> as intended. 

>Ok, I see the problem now.

>Let me talk with Andreas. As I said before, I didn't know of this problem.

It is interesting to see than Andreas did not even send a single mail.

Is there no real interest to fix up the problem?

Andreas definitely does know that libedc is _not_ GPL. He has the special 
permission to use libedc with cdrdao.

The fact that he requested and received this special permission makes it clear 
that it _cannot_ be GPL. If it was GPLd code then this special permission 
is not needed....

A major problem with cdrdao is that the fact that cdrdao states that the whole
project is GPLd makes authors of other SW believe that libedc is GPLd too.

A senseful reaction from Andreas could be to immediately remove all copies that
include the false claims and publish updated versions (e.g. cdrdao-1.1.5a, ...).
In addition, it would be desirable that Andreas contacts all Authors of related
SW that uses libedc and informs them to fix their licenses too.

When will this hapen?


J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to