From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Uninstall python 2.7 fails - alternative dependencies
Date: Tue, 2 Mar 2021 21:45:55 +0100 [thread overview]
Message-ID: <e98658b6-f2d4-8774-6d65-d2153e86b42a@gmail.com> (raw)
In-Reply-To: <CAJ1FpuM-wbPw4U-cwVz2Tf5ufjazjP0gr70GmDK9y2dbQi2XQg@mail.gmail.com>
On 02.03.2021 18:32, Doug Henderson via Cygwin wrote:
> I attempted to remove all packages related to Python 2.7 from my
> cygwin installation.
>
> I am unable to remove four packages.
>
> python2
> python27
> python27-pip
> python27-setuptools
Question:
you can not remove because they are cross dependent or because they
are pulled by other packages ?
> There are over 500 packages that require python2 and over 700 packages
> which depend2 on python2.
much less
$ cygcheck-dep -S -q -n python2| wc -w
124
$ cygcheck-dep -S -q -n python27| wc -w
145
and most are python2-* or python27-* packages
> There are also around 90 packages that refer to both python2 and
> python3 packages. I have many of these packages installed. I suspect
> that at least some of these actually require either python2 or
> python3, but do not require both.
are you sure ? May be you are counting different releases ?
Usually they should pull only one version of python.
> To assist in supporting this kind of requirement, is there a way to
> create a package whose requirements are resolved by either of several
> other packages?
Not that I am aware
> For instance, could we have a package e.g. python-alternatives, that
> when required is satisfied by either python2 or python3. This
> mechanism might be useful for dealing with any set of packages that
> work with the alternatives system.
>
> Thanks for your consideration,
> Doug
>
prev parent reply other threads:[~2021-03-02 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 17:32 Doug Henderson
2021-03-02 17:50 ` Adam Dinwoodie
2021-03-02 20:45 ` Marco Atzeri [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=e98658b6-f2d4-8774-6d65-d2153e86b42a@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).