From: Stephen Carrier <carrier@berkeley.edu>
To: L A Walsh <cygwin@tlinx.org>
Cc: Achim Gratz <Stromeko@nexgo.de>, cygwin@cygwin.com
Subject: Re: Updated: fetchmail-6.4.14-1
Date: Mon, 7 Dec 2020 09:28:04 -0800 [thread overview]
Message-ID: <20201207172804.GA14645@iguana.crashland.org> (raw)
In-Reply-To: <5FCAE08A.7090609@tlinx.org>
On Fri, Dec 04, 2020 at 05:21:14PM -0800, L A Walsh wrote:
> 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.
Today I learned there is a thing called fetchmailconf and I've been using
fetchmail for years. I agree that it should be unbundled, as python is
big dependency and manual configuration is pretty simple.
For precedent, my Fedora doesn't bundle fetchmailconf with fetchmail.
Maybe more recent Fedora versions than mine do this; I don't know.
In general, I think dependencies larger than the package it supports,
that are supporting only a non-core feature, ought to have that non-core
feature unbundled.
Stephen
prev parent reply other threads:[~2020-12-07 17:28 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
2020-12-07 17:28 ` Stephen Carrier [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=20201207172804.GA14645@iguana.crashland.org \
--to=carrier@berkeley.edu \
--cc=Stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
--cc=cygwin@tlinx.org \
/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).