public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@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 16:20:35 -0400	[thread overview]
Message-ID: <200609011620.35786.vapier@gentoo.org> (raw)
In-Reply-To: <200609011218.40499.chriswhite@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 771 bytes --]

On Friday 01 September 2006 15:18, Chris White wrote:
> On Friday 01 September 2006 11:26, Greg KH wrote:
> > 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).
>
> Well, I for one would rather not give a user the option to screw themselves
> to this magnitude with a simple "emerge cdrtools".  There's people that
> aren't reading this list, and aren't going to know what's going on.  It's
> unfair to them.

set the LICENSE variable and/or add an ewarn to the ebuild ... pushing your 
ideals by removing the package is wrong
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2006-09-01 20:27 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
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 [this message]
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=200609011620.35786.vapier@gentoo.org \
    --to=vapier@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