From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Federico Kircheis <federico.kircheis@gmail.com>
Subject: Re: [ITP] neomutt
Date: Sun, 21 Jan 2018 17:51:00 -0000 [thread overview]
Message-ID: <d77a6ae5-614d-fefb-ae22-c986313d2999@dronecode.org.uk> (raw)
In-Reply-To: <34ee4661-cc5e-b47c-1ed7-f63c705fc486@gmail.com>
On 20/01/2018 19:52, Federico Kircheis wrote:
> On 01/20/2018 07:22 PM, Marco Atzeri wrote:
[...]
> I'm not a developer of the neomutt project, and the project is hosted on
> GitHub. Therefore I simply copied the latest release on a separate
> server, in order to put it together with the .hint and .cygport file:
>
> https://fekir.info/public/neomutt
>
> Would it have been OK to provide the .hint and .cygport file per email
> (they are not big) and the link to the original package?
>
> (the official link to the latest release is
> https://github.com/neomutt/neomutt/archive/neomutt-20171215.tar.gz)
>
> I did no made the structure with "x86" as in the sample since the
> structure for both for x86 and x64 with exact the same source code,
> .hint and .cygport file.
Thanks.
Maybe it's not a good idea to describe it as a fork of Mutt, when
https://www.neomutt.org/about.html says "It's not a fork of Mutt.
It's a large set of feature patches." :)
You can name your .cygport file just "neomutt.cygport"
You need to provide at least --prefix=/usr to ./configure (currently
everything is being installed into /usr/local, not /usr), and possibly
others to satisfy the requirements of [1]
[1] https://cygwin.com/packaging-package-files.html#package_contents
next prev parent reply other threads:[~2018-01-21 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 7:43 Federico Kircheis
2018-01-20 18:22 ` Marco Atzeri
2018-01-20 19:52 ` Federico Kircheis
2018-01-21 17:51 ` Jon Turney [this message]
2018-01-21 20:18 ` Federico Kircheis
2018-01-24 18:07 ` Federico Kircheis
2018-01-26 17:01 ` Jon Turney
2018-01-28 11:38 ` Federico Kircheis
2018-01-28 14:43 ` Jon Turney
2018-01-30 5:56 ` Federico Kircheis
2018-01-31 17:55 ` Jon Turney
2018-01-31 19:21 ` Federico Kircheis
2018-02-02 19:24 ` Jon Turney
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=d77a6ae5-614d-fefb-ae22-c986313d2999@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=federico.kircheis@gmail.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).