naming of python scripts ...

[Ryan Schmidt]

On Mar 28, 2014, at 12:00, Peter Danecek wrote:

> I am realising, that some python packages which also install scripts in `bin` provide also version dependent names. For example py27-coverage (which I am looking at) is providing apart from `coverage` also `coverage2` and `coverage-2.7`. 
> 
> In combination with Macports Portgroup which places these scripts end in /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/ and links with version postfix are created. This leads to quite weird names link;
> 
> - coverage-2.7
> - coverage2-2.7
> - coverage-2.7-27

Yup, that’s weird and should be fixed.

> So wouldn't it be decidable that the Portgroup removes these additional scripts (only differing by a version postfix before the links are created?

Previously, it’s been up to each port to fix such problems. How do you propose the portgroup would fix it automatically? I’m not sure how the portgroup could know all the weird naming permutations that a module author might decide to use.