From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-pms@lists.gentoo.org, Zac Medico <zmedico@gentoo.org>,
Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Subject: Re: [gentoo-pms] Rephrasing *DEPEND
Date: Sun, 12 Jun 2011 16:49:19 +0200 [thread overview]
Message-ID: <19956.53743.875743.420679@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20110612151608.06ada65d@pomiocik.lan>
>>>>> On Sun, 12 Jun 2011, Michał Górny wrote:
>> It would be more accurate to say that it's guaranteed except for
>> cases in which circular dependencies make it impossible to
>> guarantee.
> This or other words, this makes this an unreliable feature. So,
> right now, users can't assume anything specific about dependencies
> being installed in pkg_*?
Currently, PMS only says: "These must be installed and usable before
the ebuild is treated as usable." It doesn't say anything about phases.
> Doesn't this make it actually impossible to call the installed
> application in pkg_postinst()?
I've always added such packages that I needed in pkg_postinst() to
both DEPEND and RDEPEND.
IIRC, a specific merge order in Portage is only guaranteed for DEPEND
type dependencies, but not for RDEPEND and PDEPEND.
Ulrich
next prev parent reply other threads:[~2011-06-12 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 7:32 [gentoo-pms] Rephrasing *DEPEND Michał Górny
2011-06-11 11:53 ` Ciaran McCreesh
2011-06-12 7:52 ` Michał Górny
2011-06-12 8:18 ` Ulrich Mueller
2011-06-12 9:13 ` Zac Medico
2011-06-12 13:16 ` Michał Górny
2011-06-12 14:49 ` Ulrich Mueller [this message]
2011-06-12 14:55 ` Ciaran McCreesh
2011-06-12 18:03 ` Zac Medico
2011-06-12 18:19 ` Ciaran McCreesh
2011-06-12 14:01 ` Brian Harring
2011-06-12 13:29 ` Ciaran McCreesh
2011-06-12 18:52 ` Michał Górny
2011-06-19 21:21 ` Michał Górny
2011-06-19 21:36 ` Ciaran McCreesh
2011-06-20 6:34 ` Michał Górny
2011-06-20 11:26 ` Ulrich Mueller
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=19956.53743.875743.420679@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=zmedico@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