mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Request for volunteers
Date: Sun, 30 Jun 2013 23:31:13 -0400	[thread overview]
Message-ID: <20130701033113.GV29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <30842.50.0.229.56.1372631354.squirrel@lavabit.com>

On Sun, Jun 30, 2013 at 03:29:14PM -0700, idunham@lavabit.com wrote:
> > What might be better for the near future is to get the POSIX man pages
> > project updated to match POSIX-2008+TC1 so that users of musl who want
> 
> I seem to recall running across the request for this; IIRC, the
> maintainer said he'd wait until TOG uploaded an nroff tarball for
> POSIX2008.

This sounds unlikely. My understanding was that the people who
released the "3p" man pages generated them from the published POSIX
spec (Issue 6) with the blessing of the Open Group to license them
acceptably for distribution. I don't think the Open Group gave them
nroff files though...

> The linux man pages project may focus on glibc, but they document
> differences in other Linux libc versions; it might make sense to try
> sending them patches that document musl differences.
> Besides avoiding a new project, this would be more convenient for those
> targetting multiple systems (eventually, a developer on Debian or RHEL
> would  see it while reading the man page...).

I agree this would be ideal, but I think it would require convincing
them that musl is noteworthy for inclusion in the man pages (where,
for example, uClibc, dietlibc, klibc, etc. do not seem to be
considered noteworthy). I'm not sure if we would face political
obstacles here, but we could certainly try.

> Of course, this doesn't cover the man pages for BSD-specific functions.

I think there are only a very few BSD functions in musl which are not
also in glibc. Writing man pages for these, or copying and editing the
BSD ones, would not be a huge task.

Rich


  reply	other threads:[~2013-07-01  3:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30  5:52 Rich Felker
2013-06-30 10:48 ` Szabolcs Nagy
2013-07-01  3:51   ` Rich Felker
2013-07-01 20:58     ` Szabolcs Nagy
2013-07-01 23:59       ` Rich Felker
2013-07-02  2:19         ` Szabolcs Nagy
2013-07-02  7:49           ` Rich Felker
2013-07-16 16:20             ` Szabolcs Nagy
2013-07-17 15:41               ` Rich Felker
2013-06-30 11:02 ` Daniel Cegiełka
2013-06-30 12:13   ` Rich Felker
2013-06-30 22:29     ` idunham
2013-07-01  3:31       ` Rich Felker [this message]
2013-07-01 17:42         ` Isaac
2013-07-01 17:46           ` Alex Caudill
2013-07-01 21:12           ` Isaac
2013-07-01  3:13     ` Rob Landley
2013-07-01  3:43       ` Rich Felker
2013-06-30 15:25 ` Nathan McSween
2013-06-30 22:59   ` Luca Barbato
2013-07-01 11:42 ` LM
2013-07-04 18:05 ` Rob Landley
2013-07-08  7:40   ` Szabolcs Nagy
2013-07-09  2:14     ` Rob Landley
2013-07-09  2:57       ` Matthew Fernandez
2013-07-08 14:45   ` Rich Felker
2013-07-09  2:54     ` Rich Felker
2013-07-08 14:12 ` Anthony G. Basile
2013-07-01 17:44 Felix Janda
2013-07-02  1:08 ` Michael Kerrisk (man-pages)

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=20130701033113.GV29800@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).