From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Keeping an older version of a package in the repos
Date: Mon, 18 Jan 2021 19:39:29 +0100 [thread overview]
Message-ID: <81489256-5e19-ef35-21e8-321e965cc416@gmail.com> (raw)
In-Reply-To: <DB7PR02MB3996BF916A8F0CCB71AD912FE7A40@DB7PR02MB3996.eurprd02.prod.outlook.com>
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
next prev parent reply other threads:[~2021-01-18 18:39 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 [this message]
2021-01-19 18:11 ` Hamish McIntyre-Bhatty
2021-01-19 18:36 ` Marco Atzeri
2021-01-20 17:38 ` Hamish McIntyre-Bhatty
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=81489256-5e19-ef35-21e8-321e965cc416@gmail.com \
--to=marco.atzeri@gmail.com \
--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).