Alan McKinnon <[EMAIL PROTECTED]> wrote:

> I use cdrkit because I'm sick of listening to eternal bickering about 
> licensing issues. So I use the project whose license, and 
> interpretation of the license, seemed to me to be the project that 
> would make the pedantry just go away and not feature in my life.

I am not sure whether you really intend to say this and if you did understand 
thing correctly.....

The license of the original cdrtools has been examined by specialized lawyers
and these lawyers did not see any license problem in the original software.

The license of the fork "cdrkit" has not been verified by experts. If you
follow the claims from the people behind "cdrkit" on how the GPL has to be 
interpreted for cdrtools, then cdrkit would be illegal.
This is because these people claim that GPLd software needs to be build with
a GPLd build system and this build system needs to be delivered with the source.
The "cdrkit project" however uses a 4 clause BSD build sytstem that is not 
delivered together with the source....

My question to you would be:

Do you like to support software like cdrkit that is published by people who 
attack other OSS projects?


If you like to get rid of the license debates, you need to help to prevent the
license attacks done by the people behind cdrkit. I am just a victim of these
attacks and the Linux users who are forced to live with > 50 unfixed bugs in the
fork are also victims of this attack.

Check the bug data bases from the Linux distributors who publish cdrkit instead 
of cdrtools and you will see that many serious bugs exist in the fork since 
more 
than a year and nobody is interested to fix the bugs. The original cdrtools 
software does not have known bugs. So why do you like use software with known 
bugs? 

Jörg

-- 
 EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
       [EMAIL PROTECTED]                (uni)  
       [EMAIL PROTECTED]     (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
-- 
[email protected] mailing list

Reply via email to