public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arun Raghavan" <arunisgod@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Eclass for gnome-python* split
Date: Sun, 25 May 2008 02:26:42 +0530	[thread overview]
Message-ID: <c1c082b90805241356n56a44473j7dfe8b7ffb165a3a@mail.gmail.com> (raw)
In-Reply-To: <20080524173210.4cdb510c@gentoo.org>

On Sat, May 24, 2008 at 9:02 PM, Christian Faulhammer <opfer@gentoo.org> wrote:
> "Arun Raghavan" <arunisgod@gmail.com>:
>
>> Feedback and comments (and even brickbats ;)) on the eclass are
>> invited.
>
>  * Don't install the COPYING file via the DOCS variable.
>  * The LICENSE should be kept per ebuild in my opinion

Changes made and committed -- thanks!

There was one interesting observation while I was looking at the
license for the gtkspell module. gtkspell-2 is licensed GPL-2, but
gtkspell-3 (which is not yet released and has only recently picked up
a little steam upstream) is licensed LGPL-2.1. Based on this
gtkspell-python needs to be conditionally licensed based on which
version of gtkspell it is linked against (GPL-2 if against gtkspell-2,
LGPL-2.1 if against gtkspell-3).

Something like:

if has_version =dev-python/gtkspell-2*; then
    LICENSE="GPL-2"
else
    LICENSE="LGPL-2.1"
fi

There is currently *no* way to express this in an ebuild without
invalidating the cache. For now this is just a theoretical problem,
but worthy of consideration nonetheless.

Cheers!
-- 
Arun Raghavan
(http://nemesis.accosted.net)
v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056
e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-24 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 22:01 [gentoo-dev] [RFC] Eclass for gnome-python* split Arun Raghavan
2008-05-24  7:18 ` [gentoo-dev] " Ali Polatel
2008-05-24  9:15   ` Arun Raghavan
2008-05-25 22:16   ` Mart Raudsepp
2008-05-25 22:33     ` [gentoo-dev] " Ali Polatel
2008-05-29 19:01       ` Ali Polatel
2008-05-24 15:32 ` [gentoo-dev] " Christian Faulhammer
2008-05-24 20:56   ` Arun Raghavan [this message]
2008-05-26 19:01     ` Jeroen Roovers
2008-05-26  9:27 ` [gentoo-dev] " Bo Ørsted Andresen

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=c1c082b90805241356n56a44473j7dfe8b7ffb165a3a@mail.gmail.com \
    --to=arunisgod@gmail.com \
    --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