public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John R. Graham" <n3440d@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] EAPI-1 (or >1, perhaps) Proposal:  AND Dependencies
Date: Thu, 14 Jun 2007 20:27:27 -0400	[thread overview]
Message-ID: <4671DCEF.7080009@gmail.com> (raw)

I occasionally run across a package version dependency issue that cannot
be elegantly solved by the current  dependency syntax.  Every time I've
come across this, it's boiled down to a range.  For example, package
some-cat/foo has the following versions in the tree
    some-cat/foo-4.0.0-r2
    some-cat/foo-4.1
    some-cat/foo-4.1.1
    some-cat/foo-4.1.2-r2
    some-cat/foo-4.2.1-r5
    some-cat/foo-4.3
    some-cat/foo-4.4

Now, package other-cat/bar has a runtime dependency on some-cat/foo but
it only works with the 4.1 and 4.2 slot.  The other-cat/bar ebuild was
originally composed before the some-cat/foo-4.3 package came out, so the
ebuild developer coded the runtime dependency as
    >=some-cat/foo-4.1

But, when some-cat/foo-4.3 came along, it got messy.  The only possible
solution today that I know of is
    ( || =some-cat/foo-4.1* =some-cat/foo-4.2* )
and this potentially grows over time as new versions stabilize.

What I'd really like to be able to code is a range with an AND operator,
something like this
    ( && >=some-cat/foo-4.0 <some-cat/foo-4.3 )

So, my question is, does this make sense?  Is something like this
planned for some EAPI>0?  Would it be appropriate for me (a non-dev) to
file a bug and link it to SpanKy's "EAPI-1 tracker" bug?


Thanks in advance.

- John
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2007-06-15  0:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15  0:27 John R. Graham [this message]
2007-06-15  4:52 ` [gentoo-dev] EAPI-1 (or >1, perhaps) Proposal: AND Dependencies Vlastimil Babka
2007-06-15 18:18   ` John R. Graham
2007-06-15  6:28 ` Kent Fredric
2007-06-15  8:02   ` Tobias Klausmann
2007-06-15  9:33 ` Marijn Schouten (hkBst)
2007-06-15  9:54   ` Vlastimil Babka
2007-06-15 11:08   ` John R. Graham
     [not found] ` <20070615120051.4f35ea2c@snowflake>
2007-06-15 11:45   ` Luca Barbato
2007-06-15 11:56     ` Ciaran McCreesh
2007-06-18  5:19       ` [gentoo-dev] " Steve Long
2007-06-18  6:47         ` Kent Fredric
2007-06-18 22:53           ` [gentoo-dev] " Steve Long
2007-06-19  6:38             ` Kent Fredric
2007-06-22  7:35               ` [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=4671DCEF.7080009@gmail.com \
    --to=n3440d@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