On 21-Sep-2013, Dmitry Shachnev wrote: > Script /usr/bin/python3-coverage has a versioned shebang. Then why > /usr/bin/python3.3-coverage is needed?
This is merely a modification of what the upstream code does (creates programs ‘coverage’, ‘coverage3’, ‘coverage-3.3’). I don't want to deviate too far from upstream behaviour without good reason. > Directories /usr/share/python-coverage and /usr/share/python3-coverage > have identical contents. Maybe it'll make sense to use a single directory > (i.e. /usr/share/coverage) and split it to a separate binary package > (i.e. coverage-data)? That's a good idea, and I'm hoping to get to that soon. For now, my focus is on getting a current Coverage into Debian. -- \ “Dare to be naïve.” —Richard Buckminster Fuller, personal motto | `\ | _o__) | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
