From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ranged licenses
Date: Thu, 29 Nov 2007 02:48:52 +0000 [thread overview]
Message-ID: <20071129024852.49f764f9@blueyonder.co.uk> (raw)
In-Reply-To: <20071129024027.GR14557@curie-int.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Wed, 28 Nov 2007 18:40:27 -0800
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
> I'm for ranged licenses, but I think attention needs to be paid to the
> syntax. The postfix [] form does nicely separate the version
> information from the actual license name (moreso than the traditional
> CPV atom), but the LGPL[>=2&<3] example looks to be overloading it,
> when we already have AND/OR at the higher level.
> LICENSE="|| ( Eclipse ( LGPL[>=2] LGPL[<3] ) )"
> Which is, Eclipse OR (LGPL v2 up to, but not including LGPLv3).
The ( ) form means something else for package dependencies, and so can't
be used for ranged dependencies. In particular:
( >=foo/bar-3 <foo-bar/4 )
will (correctly) be matched if both foo/bar-5 and foo/bar-1 are
installed, which can happen due to slots.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-29 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 15:00 [gentoo-dev] Ranged licenses Ciaran McCreesh
2007-11-28 19:06 ` [gentoo-dev] " Christian Faulhammer
2007-11-28 19:11 ` Ciaran McCreesh
2007-11-28 22:54 ` [gentoo-dev] " Thilo Bangert
2007-11-28 23:02 ` Ciaran McCreesh
2007-11-29 2:19 ` [gentoo-dev] " Ryan Hill
2007-11-29 2:40 ` [gentoo-dev] " Robin H. Johnson
2007-11-29 2:48 ` Ciaran McCreesh [this message]
2007-11-29 2:58 ` Robin H. Johnson
2007-11-29 3:04 ` Ciaran McCreesh
2007-11-30 10:04 ` [gentoo-dev] " Steve Long
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=20071129024852.49f764f9@blueyonder.co.uk \
--to=ciaran.mccreesh@blueyonder.co.uk \
--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