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 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.
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 dependencies this > option is enabled by default unless using source builds is disabled > 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
