unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marco van Hulten <marco@hulten.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30656@debbugs.gnu.org
Subject: bug#30656: symlink manual does not exist
Date: Thu, 01 Mar 2018 21:47:37 +0100	[thread overview]
Message-ID: <20180301214737.2040e60e@jasniac.instanton> (raw)
In-Reply-To: <87lgfb4u0s.fsf@gnu.org>

Ludovic—

Je  1 mrt 17:53 skribis Ludovic:
> Marco van Hulten <marco@hulten.org> skribis:
> 
> > The man page of ln(1) tells me there exists a symlink(2) manual page
> > (which I am used to on Unix-like systems), but it is missing:
> >
> >
> > gast@graviton ~$ man 1 ln | grep -A1 SEE\ ALSO
> > SEE ALSO
> >        link(2), symlink(2)
> > gast@graviton ~$ man 2 symlink
> > No manual entry for symlink in section 2
> > gast@graviton ~$ man symlink
> > No manual entry for symlink
> >
> >
> > Man pages of both link(2) and symlink(2) are missing.  
> 
> They are provided by the ‘man-pages’ package.

Thanks, that solves it, and it is a simple solution.

Still, in a very strict sense this is a bug.  The ln(1) man page refers
to link(2) but it does not exist (and does not inform you that you need
the man-pages package).

However, there are two reasons why it is not a big issue.  Firstly,
Guix users will likely come to know this (maybe it'll get in the Guix
documentation, or they find this bug report on the web).  Secondly, at
the bottom of the man page there is a referal to the info page that
probably includes the same information as symlink(2).  I will close the
bug report.

—Marco

      reply	other threads:[~2018-03-01 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 21:58 bug#30656: symlink manual does not exist Marco van Hulten
2018-03-01 16:53 ` Ludovic Courtès
2018-03-01 20:47   ` Marco van Hulten [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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180301214737.2040e60e@jasniac.instanton \
    --to=marco@hulten.org \
    --cc=30656@debbugs.gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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