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: Tue, 22 Apr 2008 08:09:48 +0100 [thread overview]
Message-ID: <20080422080948.10082ba1@snowcone> (raw)
In-Reply-To: <1208590988.25933.35.camel@inertia.twi-31o2.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Sat, 19 Apr 2008 00:43:08 -0700
Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> I would agree that RDEPEND should likely be installed prior to
> pkg_preinst to satisfy the dependency. After all, PDEPEND is "good
> enough" for doing packages that aren't required at
> pkg_preinst/pkg_postinst.
It's likely to, but not guaranteed to be.
> We definitely don't want to install DEPEND at the pkg_* stages, so I'd
> say the requirement there, if you're asking, is prior to src_*, if
> that matters.
If the alternatives are not being able to install from a binary at all
due to circular dependencies, or being able to install from a binary
using DEPEND to satisfy circular dependencies, which would you take?
> I'd love to have some kind of functionality to allow some kind of
> "optional" dependencies. The only real way that I could see this
> working is if we tracked what was installed as an optional dependency,
> and not reinstall it if it has been removed the next time the
> depending package is merged.
Sort of like what kdebuild has for suggested dependencies, but less
strong?
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-22 7:10 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 [this message]
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
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=20080422080948.10082ba1@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