Summary: | sys-apps/portage: allow merging RDEPEND after merging a package | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sam James <sam> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, flow, gentoo, pacho, pms |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=647824 https://issuetracker.google.com/issues/283464020 https://bugs.gentoo.org/show_bug.cgi?id=279623 https://bugs.gentoo.org/show_bug.cgi?id=902207 https://bugs.gentoo.org/show_bug.cgi?id=663324 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723, 184128, 835380 |
Description
Sam James
2023-05-20 07:57:24 UTC
We've had a note about this in the devmanual for a long time at https://devmanual.gentoo.org/general-concepts/dependencies/#runtime-dependencies: """ Items which are in RDEPEND but not DEPEND could in theory be merged after the target package. Portage does not currently do this. """ Prompted by spotting https://issuetracker.google.com/issues/283464020 (although the phrasing there might be slightly different to what we want?) This seems like a bad idea to me. Despite what PMS says, there are likely packages that require the current behavior. And I think the current behavior makes more sense anyway. I think PMS should be updated, not Portage. For example, see bug 902207. There, we have acct-group packages which are in RDEPEND in acct-user packages. The groups MUST be merged before the users, or useradd will fail. Listing the acct-group packages in DEPEND is wrong, and will be ineffective for binpkg installations. Listing the acct-group packages in IDEPEND is wrong when BROOT != ROOT. |