Re: [gentoo-dev] emerge --binpkg-changed-deps
* Zac Medico schrieb am 05.08.15 um 00:04 Uhr: On 08/04/2015 01:16 PM, Marc Schiffbauer wrote: hi all, i find it a bit hard to understand how --binpkg-changed-deps is supposed to work and what implications it has. Moreover I think the man page is not very clear about what it does: --binpkg-changed-deps [ y | n ] Tells emerge to ignore binary packages for which thecorresponding ebuild dependencies have changed since thepackages were built. In order to help avoid issues withresolving inconsistent dependencies, this option is automatically enabled unless the --usepkgonly option is enabled. Behavior with respect to changed build-time dependencies iscontrolled by the --with-bdeps option. This looks a bit confusing to me. Am I alone with that? If I understand that option right, maybe this text is better? --binpkg-changed-deps [ y | n ] When enabled tells emerge to ignore a binary package and do a source build instead if the corresponding ebuild runtimedependencies (RDEPEND) have changed in the portage tree sincethe package was built. It doesn't necessarily imply a source build, since you can have multiple binary packages available. I see. So this might be better: When enabled tells emerge to ignore a binary package if the corresponding ebuild runtime dependencies (RDEPEND) have changed in the portage tree since the package was built. With FEATURES=binpkg-multi-instance, you can have multiple local binary packages of the same package version in PKGDIR. Even without FEATURES=binpkg-multi-instance, you can also have multiple binary packages of the same package version coming from multiple binhosts. I had hoped for a feature like that and did not realize its already there, great! But thats another story.. To help avoid issues with resolving inconsistent dependenciesthis option is enabled by default unless using source builds isdisabled by the --usepkgonly option. Adding using source builds is disabled would be a valid way to clarify the meaning of --usepkgonly. Yes, I think this will improve the description. If the --with-bdeps option is also enabled, changed build-time dependencies (DEPEND) will be considered instead. Not instead, but in addition to. If the --with-bdeps option is also enabled, changed build-time dependencies (DEPEND) will also be considered. -Marc -- 0x35A64134 - 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 signature.asc Description: Digital signature
Re: [gentoo-dev] emerge --binpkg-changed-deps
On 08/04/2015 01:16 PM, Marc Schiffbauer wrote: hi all, i find it a bit hard to understand how --binpkg-changed-deps is supposed to work and what implications it has. Moreover I think the man page is not very clear about what it does: --binpkg-changed-deps [ y | n ] Tells emerge to ignore binary packages for which thecorresponding ebuild dependencies have changed since thepackages were built. In order to help avoid issues withresolving inconsistent dependencies, this option is automatically enabled unless the --usepkgonly option is enabled. Behavior with respect to changed build-time dependencies iscontrolled by the --with-bdeps option. This looks a bit confusing to me. Am I alone with that? If I understand that option right, maybe this text is better? --binpkg-changed-deps [ y | n ] When enabled tells emerge to ignore a binary package and do a source build instead if the corresponding ebuild runtimedependencies (RDEPEND) have changed in the portage tree sincethe package was built. It doesn't necessarily imply a source build, since you can have multiple binary packages available. With FEATURES=binpkg-multi-instance, you can have multiple local binary packages of the same package version in PKGDIR. Even without FEATURES=binpkg-multi-instance, you can also have multiple binary packages of the same package version coming from multiple binhosts. To help avoid issues with resolving inconsistent dependenciesthis option is enabled by default unless using source builds isdisabled by the --usepkgonly option. Adding using source builds is disabled would be a valid way to clarify the meaning of --usepkgonly. If the --with-bdeps option is also enabled, changed build-time dependencies (DEPEND) will be considered instead. Not instead, but in addition to. (Am not 100% sure whether the last sentence is technically correct) What do you think? -Marc -- Thanks, Zac
[gentoo-dev] emerge --binpkg-changed-deps
hi all, i find it a bit hard to understand how --binpkg-changed-deps is supposed to work and what implications it has. Moreover I think the man page is not very clear about what it does: --binpkg-changed-deps [ y | n ] Tells emerge to ignore binary packages for which the corresponding ebuild dependencies have changed since the packages were built. In order to help avoid issues with resolving inconsistent dependencies, this option is automatically enabled unless the --usepkgonly option is enabled. Behavior with respect to changed build-time dependencies is controlled by the --with-bdeps option. This looks a bit confusing to me. Am I alone with that? If I understand that option right, maybe this text is better? --binpkg-changed-deps [ y | n ] When enabled tells emerge to ignore a binary package and do a source build instead if the corresponding ebuild runtime dependencies (RDEPEND) have changed in the portage tree since the package was built. To help avoid issues with resolving inconsistent dependencies this option is enabled by default unless using source builds is disabled by the --usepkgonly option. If the --with-bdeps option is also enabled, changed build-time dependencies (DEPEND) will be considered instead. (Am not 100% sure whether the last sentence is technically correct) What do you think? -Marc -- 0x35A64134 - 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134
