On 10/16/2013 07:32 AM, Ben Finney wrote: >> Nearly all OpenStack projects are using testrepository. All of them >> are using python-coverage. > > That sounds like an excellent central point to make the command name > parameterisable: fix it in one place to match the Debian > ‘python-coverage’ package, and all OpenStack packages can benefit from > that. > > Note that I don't know whether that would work, but it's one option that > seems available.
Unfortunately, that's not the case. >> Many python modules are as well, and I had to patch some of them to >> avoid the problem (sorry, I can't remember which one right now...). I >> would like that it doesn't happen again, and also that our users (eg: >> developers trying to find out unit test coverage) can run the coverage >> tests without troubles. > > Patching upstream's assumptions of command names is a feature of the > landscape for Debian packagers. I don't consider that a reason to > presume ‘/usr/bin/coverage’ on Debian should refer to a Python-specific > tool. I'm not denying the fact it's possible to do what you say. I'm saying it's too much effort compared to providing /usr/bin/coverage in Debian. You are simply ignoring this point of my argumentation, which is the most important part. You have also ignore the point where I say that there's currently no conflict, so it doesn't mater. In the future *IF* there is one, then we may fix, but in the meanwhile, there is no problem at all. So why should we bother? Could you please reply to both points? Thomas P.S: Also, please keep 726...@bugs.debian.org as CC. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
