From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] cdrtools license issues
Date: Fri, 1 Sep 2006 17:57:38 +0200 [thread overview]
Message-ID: <200609011757.38410@enterprise.flameeyes.is-a-geek.org> (raw)
In-Reply-To: <200609011642.07352.pauldv@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
On Friday 01 September 2006 16:42, Paul de Vrieze wrote:
> Actually the GPL specifically states that build scripts are part of the
> source code explicitly.
And requires you to make it available, but it doesn't strictly require its
license terms to be the same. Maybe I'm confused a bit, but for what I can
understasnd of the license, he _can_ license them under CDDL... but when we
get them together with the source code, GPL still applies; which means CDDL
applies only on the makefiles by themselves. I never said it made sense,
understand me, but it doesn't actually create a GPL violation, as we still
get them as GPL'd software.
--
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-01 16:02 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ò [this message]
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
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=200609011757.38410@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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