unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Paul A. Patience" <paul@apatience.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: What is the standard path for documentation?
Date: Tue, 08 Jun 2021 16:30:34 +0000	[thread overview]
Message-ID: <31XZY1MNd0xarWiWef-MmCi5bA6kj5Cw78XR4ehAv5DhAzWpmnx8xwlGmTYV_N6FKtu5KPMT34KTZkBWU9eHvcALvJ5r_RhwmK19x-iMoxA=@apatience.com> (raw)
In-Reply-To: <87lf7kfpou.fsf@gnu.org>

Hi Ludovic,

On Tuesday, June 8th, 2021 at 09:31, Ludovic Courtès <ludo@gnu.org> wrote:

> Right, share/doc/NAME appears to be more common (perhaps we should fix
> ‘install-licence-files’).

I suppose the advantage of having the version name in the path is
allowing several versions of a library to be installed simultaneously.
Although there would be only one canonical .so file (which is a link
to whichever version is the default), the lib directory could contain
.so.VERSION files.

Of course, if those packages contain include files, the method breaks
down.
In other words, having a version suffix on the doc directory would be
beneficial only when we install libraries for linking.
But binaries in Guix get their RPATH set to the right library, so this
usecase would presumably be less common than on other distros.

All this to say, probably share/doc/NAME should be the preferred convention.

> Thus, I would not install these two files, especially since they seem to
> be redundant with Guix-supported provenance tracking.

Thanks, that's what I decided to do (i.e., delete the files).

Best regards,
Paul



      reply	other threads:[~2021-06-08 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 16:37 What is the standard path for documentation? Paul A. Patience
2021-06-08 13:31 ` Ludovic Courtès
2021-06-08 16:30   ` Paul A. Patience [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='31XZY1MNd0xarWiWef-MmCi5bA6kj5Cw78XR4ehAv5DhAzWpmnx8xwlGmTYV_N6FKtu5KPMT34KTZkBWU9eHvcALvJ5r_RhwmK19x-iMoxA=@apatience.com' \
    --to=paul@apatience.com \
    --cc=guix-devel@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).