From: Jonathan Corbet <corbet@lwn.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] Update the installation instructions with Fedora package names
Date: Sun, 11 Mar 2018 10:48:11 -0600 [thread overview]
Message-ID: <20180311104811.087495ad@lwn.net> (raw)
In-Reply-To: <20180228035552.GA6489@dcvr>
OK, I'm (finally) about to send a reworked version based on your comments.
Here's a couple of other thoughts to go with it...
> > --- a/INSTALL
> > +++ b/INSTALL
> > @@ -8,32 +8,32 @@ if they want to import mail into their personal inboxes.
> > TODO: this still needs to be documented better,
> > also see the scripts/ and sa_config/ directories in the source tree
> >
> > -It should also be possible to use public-inbox with only IMAP
> > -(or even POP(!)) access to a mailbox.
> > -
> > -standard MakeMaker installation (Perl)
> > ---------------------------------------
> > -
> > - perl Makefile.PL
>
> I'm not completely sure if moving this part makes sense, as
> Makefile.PL will warn about modules it can't find, at least.
> I think that's typical for ./configure errors in non-Perl
> projects, too.
I've opted to keep that order. The alternative is to iterate through that
"find the next missing dependency" loop, which really gets annoying after a
while. One generally wants to install dependencies before building, IMO...
> > +Beyond that, there is a long list of Perl modules required, starting with:
>
> I'm not sure if four constitutes as "long"
It does say "starting with" :)
Thanks,
jon
prev parent reply other threads:[~2018-03-11 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 23:36 [PATCH] Update the installation instructions with Fedora package names Jonathan Corbet
2018-02-28 3:55 ` Eric Wong
2018-03-11 16:48 ` Jonathan Corbet [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180311104811.087495ad@lwn.net \
--to=corbet@lwn.net \
--cc=e@80x24.org \
--cc=meta@public-inbox.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).