From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: News Item: Portage Dynamic Deps
Date: Wed, 24 Jan 2018 12:36:23 +0000 (UTC) [thread overview]
Message-ID: <p49uk7$r6b$1@blaine.gmane.org> (raw)
In-Reply-To: 23144.27401.93002.84968@a1i15.kph.uni-mainz.de
Ulrich Mueller <ulm@gentoo.org> wrote:
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --pgp+signed++Zg8D+I6sgRUw0D
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
>>>>>> On Wed, 24 Jan 2018, Martin Vaeth wrote:
>
>> Rich Freeman <rich0@gentoo.org> wrote:
>>>
>>> It would already be broken on any PMS-compliant package manager
>
>> No, it is solely the interpretation of the package manager.
>> PMS does not specify what information is stored in /var/db
>> or how that information is used.
>
> "Runtime dependencies (RDEPEND). These must be installed and usable
> before the results of an ebuild merging are treated as usable."
> https://projects.gentoo.org/pms/6/pms.html#x1-770008.1
>
> IMHO this implies that the dependencies at merge time are the relevant
> ones
IMHO this specifies what is relevant when an emerge merging happens.
Nothing more, nothing less.
_If_ one would be willing to interpret it to have a meaning also _after_
the emerge, then of course the RDEPEND in PMS can refer to the only value
which is specified in PMS, i.e. that stored in the ebuild (and not in
any database which is explicitly not specified by PMS).
In other words: _If_ one puts any unsaid interpretation into that
sentence, then this can only be dynamic deps.
next prev parent reply other threads:[~2018-01-24 12:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 7:01 [gentoo-dev] News Item: Portage Dynamic Deps Zac Medico
2018-01-22 8:24 ` Alexis Ballier
2018-01-24 20:48 ` Zac Medico
2018-01-22 9:38 ` Dirkjan Ochtman
2018-01-24 20:53 ` Zac Medico
2018-01-22 10:28 ` Andreas K. Huettel
2018-01-22 10:53 ` James Le Cuirot
2018-01-22 16:43 ` Ian Stakenvicius
2018-01-22 16:45 ` Ciaran McCreesh
2018-01-24 7:05 ` Kent Fredric
2018-01-22 16:59 ` Michał Górny
2018-01-23 12:40 ` [gentoo-dev] " Michael Palimaka
2018-01-23 13:10 ` Rich Freeman
2018-01-23 13:15 ` Michael Orlitzky
2018-01-23 13:40 ` Michael Palimaka
2018-01-23 17:12 ` Rich Freeman
2018-01-24 10:31 ` Martin Vaeth
2018-01-24 11:16 ` Ulrich Mueller
2018-01-24 12:36 ` Martin Vaeth [this message]
2018-01-24 16:36 ` Ulrich Mueller
2018-01-24 20:58 ` [gentoo-dev] " Zac Medico
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='p49uk7$r6b$1@blaine.gmane.org' \
--to=martin@mvath.de \
--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