This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [HHITP] mailutils 3.2
- From: Yaakov Selkowitz <yselkowitz at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 27 Mar 2017 14:32:49 -0500
- Subject: Re: [HHITP] mailutils 3.2
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=cygwin.com
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=none smtp.mailfrom=yselkowitz at cygwin dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 0079985363
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 0079985363
- References: <55411890-b110-bc3d-45b8-0e652b846131@cornell.edu>
On 2017-03-24 14:54, Ken Brown wrote:
This is a half-hearted ITP for GNU mailutils
(https://www.gnu.org/software/mailutils/mailutils.html). I'd like some
feedback before I proceed.
My only interest in mailutils is that it provides a utility
movemail.exe, which is used by emacs.[*] But I looked into providing a
complete build of mailutils and various subpackages along the lines of
Debian[**], and it turned out to be straightforward. My cygport file
and patches are attached. I ran the testsuite, and there were 42
failures and 3 skips out of 978 tests. The failures ought to be looked
at, but I don't this is too bad.
FWIW, even on Debian, the tests succeed until comsatd tests 2-7 all
fail, at which point make check terminates. So if those are your first
failures, it may just be the testsuite.
Not a full review, but noticed a few things:
libmailutils5_CONTENTS="
--exclude=usr/bin/
usr/bin/cyg*-5.dll
usr/lib/mailutils/*.dll"
What happens when a future version ships libmailutils6? As is, the
modules will collide. Are the modules used by the libraries directly,
or are they for the daemons?
mailutils_mh_CONTENTS="
usr/bin/mu-mh
usr/share/mailutils/mh"
A /usr/bin/mu-mh directory would violate the FHS (4.4.2: "There must be
no subdirectories in /usr/bin."). Depending on how these are used, one
of /usr/{lib,libexec}/mu-mh would make more sense.
--
Yaakov