From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: s6-man-pages update
Date: Wed, 09 Sep 2020 13:42:36 +0000 [thread overview]
Message-ID: <em27d5dea1-35d7-40ad-8d7a-ec8e33ea3e57@elzian> (raw)
In-Reply-To: <C5IV81IMLTOX.2PIEHOH0GYB1M@mussels>
>Do you think it would make sense to include the man pages in tarball
>releases of s6 software? It would help with packaging efforts across
>distros, I think. Only downside would be that, since you dislike the mdoc
>format, any changes to the man pages would have to be coordinated and
>finished by others before you made a release, if the plan is to keep
>everything consistent.
That downside is simply too big, and also, I don't want to take
responsibility in the official tarballs for content that I don't audit
myself. I don't think it would be a good trade-off, even for users.
(And that does not mean I don't trust Alexis, or other people in the
community, to do good work! If I didn't, we wouldn't even be talking
about this.)
What limits packaging efforts across distros is not the number of
packages or where and how to find them; if a distribution has a link
to get the man pages source, they will use it and will just be happy
that there are man pages. What limits packaging efforts, currently, is
only the willingness of distributions to understand and use s6.
--
Laurent
next prev parent reply other threads:[~2020-09-09 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 4:11 Alexis
2020-09-09 8:19 ` Laurent Bercot
2020-09-09 13:12 ` Alexis
2020-09-09 13:16 ` Érico Nogueira
2020-09-09 13:42 ` Laurent Bercot [this message]
2020-09-09 14:08 ` Alexis
2020-09-09 14:55 ` Laurent Bercot
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=em27d5dea1-35d7-40ad-8d7a-ec8e33ea3e57@elzian \
--to=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).