On 07/15/2015 11:31 PM, Frank Ch. Eigler wrote:
nathans wrote:
[...]
This does not affect dependencies being declared and satisfied in any
meaningful way - the argument is specious.
The argument is that it -does- affect the dependencies, because
changing that pcp.conf value breaks them.
We have had literally the *exact* same situation for many years with
$PCP_AWK_PROG and its gawk package dependency. [...]
That just means that you have faced this issue before and went with
the easier dependency-risking option. At least, awk vs. gawk is not a
subject of flux in distros, but python2 vs. 3 is.
Looking closer, the bulk of pcp.conf is of that nature: it describes
the software installation's whereabouts, so parts of pcp can find
other parts of pcp. Very few represent settings that a sysadmin
should tweak for site-specific configuration. It's kind of out of
place in /etc.
In the interests of resolving the original issue during development,
I've merged this change from Nathan's tree. If the outcome of this
discussion warrants additional changes, then they can be in follow up
commits.
One additional nit I have is that python scripts specifying pcp-python
as the interpreter might benefit from a short comment saying the wrapper
is there to use the default python interpreter for the platform, not
because we've brewed our own special python and called it python-pcp!
Cheers
|