From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: Keeping an older version of a package in the repos
Date: Wed, 20 Jan 2021 17:38:33 +0000 [thread overview]
Message-ID: <DB7PR02MB3996AD3494FCF9363AC73276E7A20@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <35dc44a8-e3f9-fe28-ca57-3ba4758239d9@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2161 bytes --]
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
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-20 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 17:57 Hamish McIntyre-Bhatty
2021-01-18 18:39 ` Marco Atzeri
2021-01-19 18:11 ` Hamish McIntyre-Bhatty
2021-01-19 18:36 ` Marco Atzeri
2021-01-20 17:38 ` Hamish McIntyre-Bhatty [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB7PR02MB3996AD3494FCF9363AC73276E7A20@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).