| 1 |
Ulrich Mueller <ulm@g.o> wrote: |
| 2 |
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156) |
| 3 |
> --pgp+signed++Zg8D+I6sgRUw0D |
| 4 |
> Content-Type: text/plain; charset=us-ascii |
| 5 |
> Content-Transfer-Encoding: 7bit |
| 6 |
> |
| 7 |
>>>>>> On Wed, 24 Jan 2018, Martin Vaeth wrote: |
| 8 |
> |
| 9 |
>> Rich Freeman <rich0@g.o> wrote: |
| 10 |
>>> |
| 11 |
>>> It would already be broken on any PMS-compliant package manager |
| 12 |
> |
| 13 |
>> No, it is solely the interpretation of the package manager. |
| 14 |
>> PMS does not specify what information is stored in /var/db |
| 15 |
>> or how that information is used. |
| 16 |
> |
| 17 |
> "Runtime dependencies (RDEPEND). These must be installed and usable |
| 18 |
> before the results of an ebuild merging are treated as usable." |
| 19 |
> https://projects.gentoo.org/pms/6/pms.html#x1-770008.1 |
| 20 |
> |
| 21 |
> IMHO this implies that the dependencies at merge time are the relevant |
| 22 |
> ones |
| 23 |
|
| 24 |
IMHO this specifies what is relevant when an emerge merging happens. |
| 25 |
Nothing more, nothing less. |
| 26 |
_If_ one would be willing to interpret it to have a meaning also _after_ |
| 27 |
the emerge, then of course the RDEPEND in PMS can refer to the only value |
| 28 |
which is specified in PMS, i.e. that stored in the ebuild (and not in |
| 29 |
any database which is explicitly not specified by PMS). |
| 30 |
In other words: _If_ one puts any unsaid interpretation into that |
| 31 |
sentence, then this can only be dynamic deps. |
Archives