unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] build: Use PKG_INSTALL_DIR
Date: Mon, 25 Mar 2024 21:44:19 -0300	[thread overview]
Message-ID: <20240325214419.5cc00e7c@tintin> (raw)
In-Reply-To: <20230418105643.1157722-1-arsen@aarsen.me>

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

Hello Arsen,

> ...
> This patch is in a similar vein to my earlier patch to Guile itself
> posted at
> https://lists.gnu.org/archive/html/guile-devel/2023-03/msg00040.html

> These came up while I was working on packaging Guile in Gentoo.
> ...

I pushed the proposed changes to the devel branch, will be part of the
next release, thanks.

> Also, on a similar note, guile-lib installs to /usr/share/guile/site/
> rather than /usr/share/guile/site/$EV (i.e. %global-site-dir instead
> of %site-dir) like other packages do.  Why is that the case?

Because, as you spotted yourself, guile-lib src modules are guile
version agnostic ... 

But i'll think about it, as it appears i am a bit lonely, to think one
shouldn't (ever) duplicate guile version agnostic code (on the same
machine), as doing so could lead to other (potentially serious)
problem(s) ...

Meanwhile, as all distro do, feel free to patch this downstream, to
install the scr modules in $prefix/share/guile/site/$EV - but the
ideal would be to have 'the machinery' to properly handle one version
of the (identical) src modules, multiple .go versions ...

David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-03-26  0:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 10:56 [PATCH] build: Use PKG_INSTALL_DIR Arsen Arsenović
2024-03-26  0:44 ` David Pirotte [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-26 22:39 Arsen Arsenović
2023-03-26 22:41 ` Arsen Arsenović

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=20240325214419.5cc00e7c@tintin \
    --to=david@altosw.be \
    --cc=arsen@aarsen.me \
    --cc=guile-devel@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.
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).