Laurent Bercot writes:
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 ... 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
Laurent Bercot writes:
Nice work! If you feel they're ready enough, I can add a link
to them
in the s6 main page right away.
Mm, thanks, but i think i'd prefer to wait until i've handled the
link issue. :-)
- The skarnet.org site is accessible in https, and is
preferred.
On Wed Sep 9, 2020 at 5:19 AM -03, Laurent Bercot wrote:
> >i've now completed the linting pass for the s6 man pages. The few remaining
> >lint issues are either commented in the sources, or aren't actually an issue
> >in this context.
> >
> >As per Laurent's request, i've also added a Makefile
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
Fair enough. :-) My thought is, to help distros with packaging, i can add tags
to the s6-man-pages repo to match the corresponding s6 version on which they
were based. So at the completion of this current process, i could add a 2.9.2.0
tag (assuming that the current docs on skarnet.org are
One thing that I forgot to mention here is that depending on the age of
the libc this might not work properly as written. Newer libc's use
datagram connections for syslog and because of that you need to
hand-write the entire s6-ipcserver chain (since the s6-ipcserver
entrypoint doesn't currently
i've now completed the linting pass for the s6 man pages. The few remaining
lint issues are either commented in the sources, or aren't actually an issue in
this context.
As per Laurent's request, i've also added a Makefile to facilitate
installation; details in the repo README:
