public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Updated: fetchmail-6.4.14-1
Date: Thu, 03 Dec 2020 18:18:55 -0800	[thread overview]
Message-ID: <5FC99C8F.4030202@tlinx.org> (raw)
In-Reply-To: <announce.878sageyug.fsf@Rainer.invalid>

On 2020/12/02 12:29, Achim Gratz wrote:
> fetchmail-6.4.14-1...
>
> This release uses the Python3 interpreter as Python2 is now EOL...
>   
----
    When I look at the binary on linux (ldd), I see no reference to any 
python
of any version.  I haven't seen the 6.4.14 package for my distro yet,
but the 6.4.12 version doesn't require python. 

    When I look at the fetchmail website, https://www.fetchmail.info/,
I see that it lists https://sourceforge.net/projects/fetchmail/ as a project
page, but with sources on https://gitlab.com/fetchmail/fetchmail/ .

    I see no mention of python being required on its info page, though I see
it mentioned on the sourceforge site.

    Should fetchmail have a dependency on python when it doesn't seem to be
needed?  Maybe put the python requiring stuff in a separate 
'python-fetchmail'
package to install that portion?

    Should I be guessing -- is it a python interface for fetchmail? 

    I know I would be surprised if I went to install (or upgrade)
fetchmail and it required me to install python.

    Seems like many(most?) other python interfaces for things reside in
'python-xxxxxx' packages -- is that an oversight for the fetchmail
code?

Tnx!
-linda

  reply	other threads:[~2020-12-04  2:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 20:29 [ANNOUNCEMENT] " Achim Gratz
2020-12-04  2:18 ` L A Walsh [this message]
2020-12-04 20:18   ` Achim Gratz
2020-12-05  1:21     ` L A Walsh
2020-12-07 17:28       ` Stephen Carrier

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=5FC99C8F.4030202@tlinx.org \
    --to=cygwin@tlinx.org \
    --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).