From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dependencies that're available at pkg_*inst
Date: Mon, 21 Apr 2008 10:00:45 +0100 [thread overview]
Message-ID: <20080421100045.76d6a4bc@snowcone> (raw)
In-Reply-To: <480C55E9.20806@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
On Mon, 21 Apr 2008 10:52:57 +0200
"Marijn Schouten (hkBst)" <hkBst@gentoo.org> wrote:
> | cat/a-1 is installed and has RDEPEND cat/b
> | cat/a-2 is to be installed and has DEPEND cat/b and RDEPEND =cat/b-2
> | cat/b-1 is installed and has RDEPEND cat/a
> | cat/b-2 is to be installed and has DEPEND cat/a and RDEPEND =cat/a-2
> |
> | Solve this and enlightenment shall be yours!
> |
> | Or a headache.
>
> This problem has the two obvious solutions: either install a-2 and
> then b-2 or the other way around.
Bzzt, wrong! Once you've installed a-2, you can't install b-2 since it
DEPENDs upon cat/a, but cat/a's run dependencies aren't satisfied, so
the dependency isn't met. And likewise for the other way around.
This problem is nowhere near as simple as you think it is.
> But to be relevant to the current discussion you need to specify
> whether or not there are any pkg_{pre,post}inst functions. If there
> are too many then it becomes unsolvable and is probably a bug, as I
> already explained:
The package manager can't sanely know whether such functions exist. (It
could, theoretically, insanely know, but forcing package managers to
be able to work that out really isn't something we want to do.)
> | Labels are a cleaner solution to this. But again, we're discussing
> | current EAPIs here.
>
> Labels seems to be another syntax for providing the same information
> as I proposed AIUI, i.e. finer-grained deps.
Labels do that and a lot more, and without the explosion in number of
metadata keys. But they're a different discussion.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-21 9:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 4:31 [gentoo-dev] Dependencies that're available at pkg_*inst Ciaran McCreesh
2008-04-19 4:45 ` Donnie Berkholz
2008-04-19 4:54 ` Ciaran McCreesh
2008-04-19 5:27 ` Donnie Berkholz
2008-04-19 5:33 ` Ciaran McCreesh
2008-04-19 7:43 ` Chris Gianelloni
2008-04-22 7:09 ` Ciaran McCreesh
2008-04-22 18:31 ` Chris Gianelloni
2008-04-19 18:53 ` [gentoo-dev] " Duncan
2008-04-19 23:55 ` Ciaran McCreesh
2008-04-21 5:17 ` [gentoo-dev] " Donnie Berkholz
2008-04-21 5:23 ` Ciaran McCreesh
2008-04-21 8:52 ` Marijn Schouten (hkBst)
2008-04-21 9:00 ` Ciaran McCreesh [this message]
2008-04-21 10:22 ` [gentoo-dev] " Duncan
2008-04-21 10:10 ` [gentoo-dev] " Luca Barbato
2008-04-21 10:15 ` Ciaran McCreesh
2008-04-21 10:05 ` Luca Barbato
2008-04-21 10:17 ` Arfrever Frehtes Taifersar Arahesis
2008-04-22 20:32 ` Doug Goldstein
2008-04-19 16:38 ` Marijn Schouten (hkBst)
2008-04-19 23:57 ` Ciaran McCreesh
2008-04-20 1:29 ` Brian Harring
2008-04-20 8:36 ` Ciaran McCreesh
2008-04-20 10:48 ` Santiago M. Mola
2008-04-22 20:31 ` Doug Goldstein
2008-04-27 9:41 ` [gentoo-dev] " Steve Long
2008-04-27 10:55 ` Ciaran McCreesh
2008-04-28 4:57 ` [gentoo-dev] " Steve Long
2008-04-28 12:13 ` Ciaran McCreesh
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=20080421100045.76d6a4bc@snowcone \
--to=ciaran.mccreesh@googlemail.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