On 19/01/2021 18:36, Marco Atzeri via Cygwin-apps wrote:
> On 19.01.2021 19:11, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> On 18/01/2021 18:39, Marco Atzeri via Cygwin-apps wrote:
>>> On 18.01.2021 18:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>>> Hi all,
>>>>
>>>> In the (hopefully!) near future I plan to package python3-wx (aka
>>>> wxPython) version 4.1.1. This is a backwards-incompatible change with
>>>> wxPython 4.0.x, so I was wondering if there was a way to retain
>>>> python3-wx 4.0.x and its binary packages in the repos after I do this
>>>> update?
>>>>
>>>> Hamish
>>>>
>>>
>>> look at the several guile packages for ideas
>>>
>>> $ cygcheck -cd | grep "^guile"
>>> ...
>>> guile1.8                                1.8.8-3
>>> guile2.0                                2.0.14-3
>>> guile2.2                                2.2.7-1
>>> guile3.0                                3.0.5-1
>>>
>>>
>>> check how to guarantee that the names are different and they
>>> do not collide as content
>>>
>>> Does any package depends on python3X-wx ?
>>> I do not see a demanding problem:
>>>
>>> $ cygcheck-dep -S -q -n python36-wx
>>>   python36-wx: is needed for ( )
>>>
>>>
>>> Regards
>>> Marco
>>
>> Yeah I guess I could name the new binary packages something like
>> python36-wx31 etc, but that might be a bit ugly. I'm not sure if Cygwin
>> has a convention for that.
>>
>> I was more thinking about any 3rd party applications that may depend on
>> it, but perhaps that's not too much of a concern.
>>
>> Hamish
>>
>
>
> I was referring to collision of file names
>
> $ cygcheck -l python38-wx |grep bin
> /usr/bin/helpviewer-py38
> /usr/bin/img2png-py38
> /usr/bin/img2py-py38
> /usr/bin/img2xpm-py38
> /usr/bin/pycrust-py38
> /usr/bin/pyshell-py38
> /usr/bin/pyslices-py38
> /usr/bin/pyslicesshell-py38
> /usr/bin/pywxrc-py38
> /usr/bin/wxdemo-py38
> /usr/bin/wxdocs-py38
> /usr/bin/wxget-py38
>
Ah yes, that would be a problem. This endeavour is probably not worth it
then with no internal dependencies.

Hamish