public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 03:04:24 +0000	[thread overview]
Message-ID: <20071129030424.1a4baaa0@blueyonder.co.uk> (raw)
In-Reply-To: <20071129025807.GT14557@curie-int.orbis-terrarum.net>

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

On Wed, 28 Nov 2007 18:58:07 -0800
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
> > 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.
> 
> Ok, I revise that for slots then:
> LICENSE="|| ( Eclipse ( LGPL[>=2] !LGPL[>=3] ) )"
> (which is more in line with my description of the license string).
> The !/NEGATION might be inside the [] blocks, since the AND and OR
> operators are.

This gets really messy and hard to define sanely when you consider
things like slot and use dependencies. It also involves a lot of
duplication of package names. You're also breaking the package form

    ( >=foo/bar-2 !>=foo/bar-3 )

which has a different existing meaning (as do all other forms based
around repeating the cat/pkg part inside a block).

Really, the sanest way to do ranged dependencies is by extending the
syntax of individual package / license dep specs, and the postfix
[opver&opver] / [opver|opver] form is the least icky proposal.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-11-29  3:07 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
2007-11-29  2:58             ` Robin H. Johnson
2007-11-29  3:04               ` Ciaran McCreesh [this message]
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=20071129030424.1a4baaa0@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