From: Jon Turney <jon.turney@dronecode.org.uk>
To: gs-cygwin.com@gluelogic.com, Peter Lai <cowbert@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Why python > 36 so many dependencies?
Date: Thu, 25 Apr 2024 19:18:12 +0100 [thread overview]
Message-ID: <46622636-88b2-4af9-a5ae-6e37f7262a74@dronecode.org.uk> (raw)
In-Reply-To: <ZiqW4fbS5fq-f4MQ@xps13>
On 25/04/2024 18:46, gs-cygwin.com--- via Cygwin wrote:
> On Thu, Apr 25, 2024 at 10:19:05AM -0400, Peter Lai via Cygwin wrote:
>> Why does installing python > py36 result in bringing in so many
>> dependencies like libXdmcp etc, when the intent is to just run python
>> interpreter from cli? Is this because of the way it's built for cygwin? I
>> build python all the time in NetBSD using pkgsrc and in FreeBSD ports,
>> without needing all of those deps. I don't know much about how cygport
>> works, is there a repo of cygport files I can look at?
>
> The load at https://cygwin.com/git/ is too high at the moment
> and I get "503 - The load average on the server is too high"
https://cygwin.com/cgit/ may behave better.
> Take a look at some mirrors.
>
> For cygport code:
> https://github.com/cygwin/cygport
This is just a mirror of https://cygwin.com/cgit/cygwin-apps/cygport/
You should probably take a look at the cygport manual () before reading
the source code.
> Lots of individual repositories under here with cygport projects
> https://github.com/cygwinports/
No, don't look there!
Those repositories haven't been updated for some time, and really should
really be archived, but the owner is too busy.
> e.g.
> https://github.com/cygwinports/python36
https://cygwin.com/cgit/cygwin-packages/python36/
prev parent reply other threads:[~2024-04-25 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 14:19 Peter Lai
2024-04-25 17:46 ` gs-cygwin.com
2024-04-25 18:18 ` Jon Turney [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=46622636-88b2-4af9-a5ae-6e37f7262a74@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cowbert@gmail.com \
--cc=cygwin@cygwin.com \
--cc=gs-cygwin.com@gluelogic.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).