From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH v2] Clarify Inline::C dependency (optional on Linux, required elsewhere)
Date: Sat, 2 Sep 2023 20:56:27 +0000 [thread overview]
Message-ID: <20230902205627.M260262@dcvr> (raw)
In-Reply-To: <20230902224501+0200.863993-stepnem@smrk.net>
Štěpán Němec <stepnem@smrk.net> wrote:
> On Sat, 02 Sep 2023 19:44:07 +0000
> Eric Wong wrote:
>
> > Perhaps the per-module "optional, for .." statements should be
> > "only for ...".
>
> Well, if that's really true (i.e., they're not needed/useful for
> anything else)...
>
> I guess you see INSTALL as mainly for public-inbox without lei (and
> indeed the first sentence is "This is for folks who want to set up their
> own public-inbox instance."), so from that perspective saying "optional"
> about something that is optional for public-inbox but required for lei
> makes sense, but lei is then mentioned repeatedly in the dependencies
> section, and it seems a safe bet there are much more people using lei
> than there are people setting up public-inbox instances, so I'm not sure
> maintaining that perspective in INSTALL is the best way to help those
> users.
Perhaps a separate "INSTALL-lei" file is warranted. lei is newer,
and parts of it still somewhat unrefined/experimental IMHO.
> Then again, maybe it's just in my head and I might as well let such
> users speak for themselves if they exist and ever wish to do so.
Thanks for the different perspective. In my mind, public-inbox-mda
and PublicInbox::WWW were "first" and everything came after.
> So here's just a reroll with your suggestions implemented:
>
> -- 8< --
> Subject: [PATCH v3] Clarify Inline::C dependency (optional on Linux, required
> elsewhere)
Thanks, applied as commit 18c6c4e81dca1d81f6ff2bb284554b5fca2ef163
prev parent reply other threads:[~2023-09-02 20:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 5:10 [PATCH 0/7] various build fixes + OpenBSD compat Eric Wong
2023-08-30 5:10 ` [PATCH 1/7] treewide: drop MSG_EOR with AF_UNIX+SOCK_SEQPACKET Eric Wong
2023-08-30 5:10 ` [PATCH 2/7] Makefile.PL: fix syntax for ASan and valgrind targets Eric Wong
2023-08-30 5:10 ` [PATCH 3/7] Makefile.PL: depend on autodie, at least for tests Eric Wong
2023-08-30 5:10 ` [PATCH 4/7] t/kqnotify: improve test reliability on OpenBSD Eric Wong
2023-08-30 5:10 ` [PATCH 5/7] xap_helper.h: don't compress debug sections " Eric Wong
2023-08-30 5:10 ` [PATCH 6/7] xap_helper.h: limit stderr assignment to glibc+FreeBSD Eric Wong
2023-08-30 5:10 ` [PATCH 7/7] xap_helper.h: fix double-free on OpenBSD hdestroy Eric Wong
2023-08-30 12:34 ` [PATCH 0/7] various build fixes + OpenBSD compat, " Štěpán Němec
2023-08-30 21:18 ` Eric Wong
2023-08-31 9:11 ` Štěpán Němec
2023-08-31 17:26 ` Štěpán Němec
2023-09-01 11:09 ` Eric Wong
2023-09-02 10:54 ` Štěpán Němec
2023-09-02 11:07 ` [PATCH v2] Clarify Inline::C dependency (optional on Linux, required elsewhere) Štěpán Němec
2023-09-02 18:50 ` Eric Wong
2023-09-02 19:08 ` Štěpán Němec
2023-09-02 19:44 ` Eric Wong
2023-09-02 20:45 ` Štěpán Němec
2023-09-02 20:56 ` Eric Wong [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=20230902205627.M260262@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=stepnem@smrk.net \
/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).