Summary: | emerge -u --getbinpkg world does not fetch updatable package (unless --with-bdeps=y) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robert Spillner <trent2> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | trent2, zmedico |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=598444 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 427938 | ||
Bug Blocks: |
Description
Robert Spillner
2024-03-07 00:00:51 UTC
Unfortunately the --with-bdeps automatic behavior from bug 598444 is not enabled for -g or -k. (In reply to Zac Medico from comment #1) > Unfortunately the --with-bdeps automatic behavior from bug 598444 is not > enabled for -g or -k. Thanks for the pointer to the reason of this; I haven't been thinking about build-dependencies. So I read the emerge manual and for the "--with-bdeps"-options it says "Since many users of binary packages do not want unnecessary build time dependencies installed, this option is not automatically enabled for installation actions when the --usepkg option is enabled. In order to pull in build time dependencies for binary packages with --usepkg, --with-bdeps=y must be specified explicitly. This also applies to options that enable the --usepkg option implicitly, such as --getbinpkg." So this is actually expected behaviour, isn't it? So why keep this as a confirmed bug then? (In reply to Robert Spillner from comment #2) > So this is actually expected behaviour, isn't it? So why keep this as a > confirmed bug then? If there's nothing lacking in the documentation then yeah I think we can just close this. |