Hi -
nathans wrote:
> [...]
> > But thinking of it as a user option (something changeable within
> > /etc/pcp.conf) is odd:
>
> Not really, and pcp.conf is only one avenue of modifying it - its just
> like using /usr/bin/env to allow environment-driven alternatives. [...]
You elided the key part of my concern:
# this is a packaging decision (so dependencies can be declared &
# satisfied) rather than a sysadmin whim.
So, with choice of python interpreter being a run-time alternative,
how do you intend to address dependencies? Should pcp.spec require
python or python3 & related libraries? Sure, you can make it
by-default-match the one that pcp.conf will be preconfigured for. But
if the sysadmin changes it, the software will break (since the other
python{3,2} dependencies are no longer assuredly satisfied by the
packaging system).
I suggest against making this setting run-time configurable a la
pcp.conf or the environment, and instead hard-coding it within the
wrapper.
- FChE
|