All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Guillem Jover <guillem@hadrons.org>, linux-man@vger.kernel.org
Subject: Re: Order priority issues for special 3type sub-section
Date: Thu, 7 Mar 2024 11:24:12 +0100	[thread overview]
Message-ID: <ZemVzKM0HgbP-QPA@debian> (raw)
In-Reply-To: <Zek9RRW28ZinfkxB@thunder.hadrons.org>

[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]

On Thu, Mar 07, 2024 at 05:06:29AM +0100, Guillem Jover wrote:
> > I think projects shouldn't use their own subsection.  They should
> > instead use the same sections, in this case 3type, and use LIBRARY to
> > document the library needed to get the thing.
> 
> I don't think this works as a general rule, because different projects
> might want to document things that live in different namespaces. For
> things that are going to be "enforced" to share the same namespace
> such as programs, or header files, then that's fine. But for function
> interfaces or language features, for example which might be the same
> on different implementations using sub-section makes sense to me. For
> example it seems it would be rather inappropriate to document perl's
> if(3perl) as if(3). :)

Hmmm, yeah, other languages live in other namespaces, so they do well
using their own subsection.

> > And in cases wher various projects offer the same page exact page, maybe
> > /etc/alternatives should decide.
> 
> alternatives are supposed to be used for the same interface, not for
> conflicting and unrelated ones, in this case if these document stuff
> that is completely different then that would not seem appropriate.

But C libraries live in the same namespace as libc, so they do indeed
implement the same interface (hopefully; I hate it when a library
implements something different with the name of something already
existing) in a different library.

This is the case of libbsd.

Though I understand other systems that you support have different
rules, such as using 3m for libm stuff, so for supporting those systems,
I understand you prefer to stay in 3bsd.

> In this particular case, what I'll be doing is to remove the
> timeval(3bsd), timespec(3bsd) links everywhere, and stop installing
> the TIMEVAL_TO_TIMESPEC(3bsd) and TIMESPEC_TO_TIMEVAL(3bsd) on glibc
> based systems, and check on what others these are already provided,
> and install those there conditionally.

Good.

Have a lovely day!
Alex

> 
> Thanks,
> Guillem

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-07 10:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 23:22 Order priority issues for special 3type sub-section Guillem Jover
2024-03-07  0:42 ` Alejandro Colomar
2024-03-07  1:08   ` Oskari Pirhonen
2024-03-07  2:05     ` Alejandro Colomar
2024-03-07  2:09     ` Mail-Followup-To header (was: Order priority issues for special 3type sub-section) Alejandro Colomar
2024-03-07  9:37       ` Lennart Jablonka
2024-03-07 10:37         ` Alejandro Colomar
2024-03-07  4:06   ` Order priority issues for special 3type sub-section Guillem Jover
2024-03-07 10:24     ` Alejandro Colomar [this message]
2024-03-20  9:18     ` Guillem Jover
2024-03-20 10:07       ` Alejandro Colomar

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=ZemVzKM0HgbP-QPA@debian \
    --to=alx@kernel.org \
    --cc=guillem@hadrons.org \
    --cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.