public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris White <chriswhite@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] cdrtools license issues
Date: Fri, 1 Sep 2006 13:54:24 -0700	[thread overview]
Message-ID: <200609011354.29422.chriswhite@gentoo.org> (raw)
In-Reply-To: <200609011643.12587.vapier@gentoo.org>

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

On Friday 01 September 2006 13:43, Mike Frysinger wrote:
> if you werent implying "remove the package" when you said "not give a user
> the option", then what else could you possibly be talking about
> -mike

Working on an the presented alternative, debburn, like I've been saying in 
pretty much all my emails!  This way we can say "Hey, if you're worried about 
the licensing for this package, here's an alternative".  Yes, I'd also like 
to find the alternative closest to cdrtools that's GPL because the vast 
majority of CD burning packages out there use it.  Heck, dvdrtools is GPL, 
you could use that.  As long as we have an alternative to point users to, 
good.  THAT'S what I'm trying to say.

-- 
Chris White
Gentoo Developer aka:
ChrisWhite		cpw
ChrisWhite|Work	WhiteChocolate
VanillaWhite		Whitey
WhiteLight		WhiteCheese
WhiteSugar		WhiteButter
WhiteWall		WhiteLemon
WhiteApple		WhiteBlanket
WhiteEnergy		WhiteWhite

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

  reply	other threads:[~2006-09-01 20:58 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
2006-09-01 20:28       ` Chris White
2006-09-01 20:43         ` Mike Frysinger
2006-09-01 20:54           ` Chris White [this message]
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=200609011354.29422.chriswhite@gentoo.org \
    --to=chriswhite@gentoo.org \
    --cc=gentoo-dev@lists.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