From: David Pirotte <david@altosw.be>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: source and compiled file installtion locations
Date: Sat, 5 May 2018 21:03:14 -0300 [thread overview]
Message-ID: <20180505210314.7339730a@capac> (raw)
In-Reply-To: <20180503021534.0abd1de5@capac>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Hello Guilers,
> 1- no --use-guile-site
>
> in this case, imo, locations should be
>
> $(datarootdir)/<project-name> [ source
FWIW,
This is what guile-gnome does, and it also does it in $(libdir), $(includedir) ...,
It does it using guile-gnome API version, not guile effective version, which I also
think 'projects' should do, so currently, guile-gnome pure scheme modules land
in:
$(datarootdir)/guile-gnome-2
[ except for the doc, installed in
[ $(docdor)/guile-gnome-platform/
The only module that guile-gnome installs in $(datarootdir)/guile/site (and not
$(datarootdir)/guile/site/GUILE_EFFECTIVE_VERSION as I also claim we should not do
this) is gnome-2, a module that users import to 'inform' guile of source, lib
locations (which they also can do sing the guile-gnome-2 script ...)
Cheers,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-06 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 5:15 source and compiled file installtion locations David Pirotte
2018-05-06 0:03 ` David Pirotte [this message]
2018-05-06 8:56 ` Chris Vine
2018-05-06 22:17 ` David Pirotte
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=20180505210314.7339730a@capac \
--to=david@altosw.be \
--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).