From: L A Walsh <cygwin@tlinx.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: cygwin@cygwin.com
Subject: Re: Updated: fetchmail-6.4.14-1
Date: Fri, 04 Dec 2020 17:21:14 -0800 [thread overview]
Message-ID: <5FCAE08A.7090609@tlinx.org> (raw)
In-Reply-To: <87tut1wcis.fsf@Rainer.invalid>
On 2020/12/04 12:18, Achim Gratz wrote:
> L A Walsh writes:
>
>> I see no reference to any python of any version.
>>
>
> Yes, the package does depend on it, and as noted in the announcement it depends specifically on python36.
>
----
So, people who configure fetchmail with the man page and have never used
fetchmailconf should get in the habit of ignoring package requirements?
Not sure
how good that is.
>
>> 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.
>>
>
> Oh please, it isn't all that hard to figure out that fetchmailconf is
> implemented in Python.
>
Oh please yourself! :^)
I've never used fetchmailconf in using fetchmail. fetchmail doesn't
require python -- a special "fetchmailconf" requires it, which wasn't
part of fetchmail when I started using it -- for that matter it still isn't
part of my linux distro's fetchmail.
I read the manpage and edited .fetchmailrc in my home directory.
I started using fetchmail before fetchmailconf was around, AFAIK.
Maybe putting fetchmailconf in its own package would be appropriate?
next prev parent reply other threads:[~2020-12-05 1:22 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
2020-12-04 20:18 ` Achim Gratz
2020-12-05 1:21 ` L A Walsh [this message]
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=5FCAE08A.7090609@tlinx.org \
--to=cygwin@tlinx.org \
--cc=Stromeko@nexgo.de \
--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).