Re: Claiming ‘/usr/bin/coverage’ for a Python-specific programmer tool

2013-10-16 Thread Thomas Goirand
On 10/16/2013 02:05 PM, Ben Finney wrote: > Thomas Goirand writes: > >> On 10/15/2013 06:21 PM, Tristan Seligmann wrote: >>> What sort of upstream "source code" would be using the /usr/bin >>> wrapper at all? (I ask this question without prejudice; I can >>> obviously imagine some ways this might

Re: Using update-alternatives for /usr/bin provided binaries

2013-10-16 Thread Thomas Goirand
On 10/16/2013 01:52 PM, Tristan Seligmann wrote: > On Tue, Oct 15, 2013 at 1:47 PM, Thomas Goirand wrote: >> On 10/15/2013 06:21 PM, Tristan Seligmann wrote: >>> What sort of upstream "source code" would be using the /usr/bin >>> wrapper at all? (I ask this question without prejudice; I can >>> ob

Re: Using update-alternatives for /usr/bin provided binaries

2013-10-16 Thread Thomas Goirand
On 10/16/2013 02:20 PM, Robert Collins wrote: > I think it's reasonable to get OpenStack to look for python-coverage > to run it's tests when using a system package. Or use python -m > coverage. 'coverage' is indeed super generic and the precedent within > Debian for the package is to call the bina