public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Carsten Lohrke <carlo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Eigen and GPL-2 exception - is a new licence required?
Date: Sat, 12 May 2007 14:27:43 +0200	[thread overview]
Message-ID: <200705121427.50624.carlo@gentoo.org> (raw)
In-Reply-To: <200705121242.03449.cryos@gentoo.org>

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

No. LICENSE="GPL-2 some-exception" suffices. That said, we suck at our 
licensing information badly. E.g. every single ebuild linking against OpenSSL 
has (or at least needs to have) a linking exeption. We don't flag this 
anywhere. More important, what's with optional dependencies!? We don't 
support 

LICENSE="GPL-2 ssl? ( openssl-exception)"

style LICENSE content at all iirc. Similar for all the patent-encumbered 
multimedia libs, which can't be distributed as binaries, but are not blocked 
by some bindist feature flag or so.


Carsten

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2007-05-12 12:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 11:41 [gentoo-dev] Eigen and GPL-2 exception - is a new licence required? Marcus D. Hanwell
2007-05-12 12:27 ` Carsten Lohrke [this message]
2007-05-12 12:32   ` Carsten Lohrke
2007-05-12 12:54   ` Bryan Østergaard
2007-05-12 13:00   ` Harald van Dijk
2007-05-12 13:13     ` Carsten Lohrke
2007-05-12 13:38       ` Harald van Dijk
2007-05-12 14:22         ` Carsten Lohrke
2007-05-12 14:38           ` Marcus D. Hanwell
2007-05-12 14:43           ` Harald van Dijk
2007-05-12 13:03   ` Mike Frysinger
2007-05-12 12:57 ` Petteri Räty
2007-05-12 19:24 ` Kevin F. Quinn
2007-05-12 19:40   ` Petteri Räty
2007-05-13 13:15     ` Marcus D. Hanwell

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=200705121427.50624.carlo@gentoo.org \
    --to=carlo@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