| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: python3 woes on f22 |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Mon, 13 Jul 2015 11:16:29 -0400 |
| Cc: | Mark Goodwin <mgoodwin@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <227885808.37023848.1436780775020.JavaMail.zimbra@xxxxxxxxxx> (Nathan Scott's message of "Mon, 13 Jul 2015 05:46:15 -0400 (EDT)") |
| References: | <5594A1B5.5090003@xxxxxxxxxx> <y0mbnfhvx03.fsf@xxxxxxxx> <55A2FFBB.5000803@xxxxxxxxxx> <227885808.37023848.1436780775020.JavaMail.zimbra@xxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
nathans wrote:
> [...]
> Perhaps we could generalise it into a pcp-env(1), which could expand the
> $PCP_PYTHON_PROG from pcp.conf, for use in shebang lines like:
> #!/usr/bin/pcp env $PCP_PYTHON_PROG
Note that UNIX shebang lines only permit a single argument ("env"),
so you'd need a combined front-end like /usr/bin/pcp-env or something.
But thinking of it as a user option (something changeable within
/etc/pcp.conf) is odd: this is a packaging decision (so dependencies
can be declared & satisfied) rather than a sysadmin whim.
- FChE
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1242463] New: RFE: provide a method to query set of metrics with aliases, bugzilla |
|---|---|
| Next by Date: | Reply .....ASAP, Mr.John |
| Previous by Thread: | Re: [pcp] python3 woes on f22, Nathan Scott |
| Next by Thread: | Re: python3 woes on f22, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |