From: Chris White <chriswhite@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] cdrtools license issues
Date: Fri, 1 Sep 2006 15:15:35 -0700 [thread overview]
Message-ID: <200609011515.38647.chriswhite@gentoo.org> (raw)
In-Reply-To: <44F8AA5E.7060405@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Friday 01 September 2006 14:47, Jakub Moc wrote:
> Yeah, that's the previous fork that's been package.masked recently
> (homepage returns nifty internal server error now, we sure can expect a
> rapid development there).
Hey ruby's had their entire server down for 2 days! We sure can expect rapid
development there! Hey MySQL's server went down yesterday! We sure can
expect rapid development there!
> So, we apparently need even more forks now,
> like debburn. When will people learn... :/
One more fork, sounds like "even more fork(s)" to me! It has a reason for
being forked too, this isn't like random "Hey let's go fork cause we feel
like it". The reason why I'm recommending looking into debburn is because
it's a possible alternative to cdrtools which doesn't require thinking into
the license, and possibly screwing onself over. Heck, would you rather the
user had no option than not installing the one package that powers just about
all off the linux cd burning programs out there?
--
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 --]
next prev parent reply other threads:[~2006-09-01 22:18 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
2006-09-01 21:47 ` Jakub Moc
2006-09-01 22:15 ` Chris White [this message]
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=200609011515.38647.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