public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: media-optical@gentoo.org
Subject: Re: [gentoo-dev] cdrtools license issues
Date: Fri, 1 Sep 2006 11:26:08 -0700	[thread overview]
Message-ID: <20060901182608.GB9973@kroah.com> (raw)
In-Reply-To: <200609011444.59711.carlo@gentoo.org>

On Fri, Sep 01, 2006 at 02:44:59PM +0200, Carsten Lohrke wrote:
> As discussed here?, the author of cdrtools, J?rg Schilling, violates the GPL 
> in his application, by building GPL software with CDDL licensed makefiles as 
> well as linking mkisofs to libscg, which he relicensed to CDDL lately. Debian 
> seems to fork? cdrtools therefore.
> 
> Imho we have to remove the partly and incompatible relicensed cdrtools-2.01.01 
> alpha ebuilds from the tree.

No, we should just stop distributing the prebuild image in our release
and live cds.  We do not have to do anything with the package in
portage, as it is the user who builds cdrtools that does the violating
(and only if they then redistribute the built binary).

Same rule as the binary kernel modules situation.

So we are just fine, one of the advantages of being a source-based
distro :)

thanks,

greg k-h
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-09-01 18:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01 12:44 [gentoo-dev] cdrtools license issues Carsten Lohrke
2006-09-01 12:51 ` [gentoo-dev] " Lars Weiler
2006-09-01  0:00   ` Christian 'Opfer' Faulhammer
2006-09-01 13:24   ` Carsten Lohrke
2006-09-01 13:45     ` Luis Medinas
2006-09-01 14:59       ` Carsten Lohrke
2006-09-05  3:38         ` Luis Medinas
2006-09-05  6:19           ` Diego 'Flameeyes' Pettenò
2006-09-05  6:57           ` Mike Frysinger
2006-09-05 11:11           ` Lars Weiler
2006-09-05 12:20           ` Luca Barbato
2006-09-01 13:08 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2006-09-01  0:00   ` [gentoo-dev] " Christian 'Opfer' Faulhammer
2006-09-01 13:24     ` Diego 'Flameeyes' Pettenò
2006-09-01  0:00       ` Christian 'Opfer' Faulhammer
2006-09-01 13:36   ` [gentoo-dev] " Paul de Vrieze
2006-09-01 14:31     ` Diego 'Flameeyes' Pettenò
2006-09-01 14:38       ` Ciaran McCreesh
2006-09-01 14:42       ` Paul de Vrieze
2006-09-01 15:57         ` Diego 'Flameeyes' Pettenò
2006-09-01 18:26 ` Greg KH [this message]
2006-09-01 19:18   ` Chris White
2006-09-01 19:46     ` Jakub Moc
2006-09-01 19:57       ` Chris White
2006-09-01 20:19         ` Jakub Moc
2006-09-01 20:20     ` Mike Frysinger
2006-09-01 20:28       ` Chris White
2006-09-01 20:43         ` Mike Frysinger
2006-09-01 20:54           ` Chris White
2006-09-01 21:47             ` Jakub Moc
2006-09-01 22:15               ` Chris White
2006-09-01 22:35                 ` Alec Warner
2006-09-01 20:31       ` Olivier Crete
2006-09-05 11:16         ` Lars Weiler
2006-09-01 20:19   ` Mike Frysinger
2006-09-02 15:07   ` Carsten Lohrke
2006-09-02  1:13 ` Peter Gordon
2006-09-02  2:32   ` Greg KH
2006-09-02  3:10     ` Peter Gordon
2006-09-02  4:01     ` Alec Warner
2006-09-02  5:39       ` Mike Frysinger
2006-09-05 11:19     ` Lars Weiler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060901182608.GB9973@kroah.com \
    --to=gregkh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=media-optical@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox