Package: pbuilder
Version: 0.231 (& current git version at salsa.debian.org)
By inspecting the code of pdebuild and pdebuild-checkparams:
1. When using the '--use-pdebuild-internal' option, then
PBUILDERSATISFYDEPENDSCMD is passed explicitly
to the script that is executed inside the chroot, at line:
67 --pbuildersatisfydepends "$PBUILDERSATISFYDEPENDSCMD"
2. When not using the '--use-pdebuild-internal' option, then
the remaining command line arguments are passed to
pbuilder --build, at line:
107 "$@" \
Those are pbuilder arguments, since pdebuild-checkparams,
by shifting all recognised by pdebuild options, eats everything
up to the '--'.
So, the '--pbuildersatisfydepends' option is not honored in the
second case. This IMHO is a bug for the 'pdebuild' man page,
since this distinction is not mentioned in the text.
This is not a bug for pbuilder, since it does not honor this option
anyway; thus passing it by pdebuild at the second case would be
meaningless. The selection of satisfydepends has been delegated
to the system administrator, through the 'pbuilder-satisfydepends'
symlink at '/usr/lib/pbuilder/'. In the usual case, the developer is also
the administrator of his/her own computer and can set the symlink.
I don't currently have an opinion on whether a more "flexible"
approach on this subject (i.e. add the feature to the second
pdebuild case also) would be desirable, or not.
Gheers,
Georgios
