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: Sun, 20 Apr 2008 00:57:28 +0100 [thread overview]
Message-ID: <20080420005728.2d4d2c70@snowcone> (raw)
In-Reply-To: <480A1FEE.4020604@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]
On Sat, 19 Apr 2008 18:38:06 +0200
"Marijn Schouten (hkBst)" <hkBst@gentoo.org> wrote:
> Every package dependency in DEPEND is installed and usable before
> src_unpack starts, right? So is the question here whether or not they
> can be uninstalled right before pkg_{pre,post}inst starts?
If we're using binaries, DEPEND is usually ignored.
> I don't know what the general use of pkg_preinst is, but in
> pkg_postinst the package itself should be runnable, so its RDEPENDS
> should be installed and usable at this point. So perhaps we should
> define that "usable" means "each of its RDEPENDs is installed and has
> had its pkg_postinst function run". The recursion of that definition
> then comes from the requirement that RDEPENDs should be usable before
> pkg_postinst starts running.
No good. That prevents RDEPEND <-> RDEPEND cycles from being solved,
and the package manager has to be able to solve that.
> If only one of those packages has a pkg_postinst then it is still
> solvable. If they both have a pkg_postinst then one of those is
> probably not essential for the actual usability of the package and
> should be removed. A final possibility is that the pkg_postinsts are
> both necessary for a fully functional package but not for the
> functionality used in the other pkg_postinst. If this is the case,
> then perhaps we should specify deps according to which ebuild phase
> they are necessary for?
Not with current EAPIs we can't.
> SRC_UNPACK_DEP="app-arch/unzip"
> SRC_COMPILE_DEP="dev-scheme/bigloo"
> SRC_INSTALL_DEP=""
Labels are a cleaner solution to this. But again, we're discussing
current EAPIs here.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-19 23:57 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
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 [this message]
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=20080420005728.2d4d2c70@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