From: Jack Hill <jackhill@jackhill.us>
To: Alex Sassmannshausen <alex@pompo.co>
Cc: 34181@debbugs.gnu.org
Subject: bug#34181: guile-hall: no code for module (config)
Date: Mon, 28 Jan 2019 20:00:40 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.1901281715170.6623@marsh.hcoop.net> (raw)
In-Reply-To: <87sgxgfyt7.fsf@pompo.co>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
On Fri, 25 Jan 2019, Alex Sassmannshausen wrote:
> OK, I did some research. The issue is as follows:
> - Virtually all guile packages declare guile an input, but not a
> propgated input. This seems to make Guile available in the
> environment, but without the Guile environment paths defined.
> - Guile-DBI on the other hand seems to declare guile a propagated
> input. This causes the environment paths to be set.
> - Similarly, when you install in your profile:
> + installing guile too will encourage you to set up the environment
> path.
> + installing only the library will not.
> + installing only guile will not do this either (see the example in
> the manual, at
> https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-package.html#index-search-paths
> - When you install, either in environment, or in profile, both guile and
> a guile-library, the env variables are set/reported correctly.
>
> This looks like it is intended behaviour.
>
> Please test and let me know if this resolves the issue for you!
I am happy to confirm that in an environment with both guile and
guile-hall, the hall command works as expected (regardless of the
setting of the correct paths using hall without guile is silly since it is
a tool to aid in the development of guile projects ☺).
However, I think that Ricardo might be right, and the hall cli should wrap
these paths, since hall is an executable and not only a guile library.
Best,
Jack
next prev parent reply other threads:[~2019-01-29 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 16:35 bug#34181: guile-hall: no code for module (config) Jack Hill
2019-01-23 17:11 ` Alex Sassmannshausen
2019-01-25 15:41 ` Jack Hill
2019-01-25 16:24 ` Ricardo Wurmus
2019-01-25 16:34 ` Catonano
2019-01-26 9:41 ` Alex Sassmannshausen
2019-01-25 17:10 ` Alex Sassmannshausen
2019-01-29 1:00 ` Jack Hill [this message]
2019-01-31 15:26 ` Ricardo Wurmus
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=alpine.DEB.2.20.1901281715170.6623@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=34181@debbugs.gnu.org \
--cc=alex@pompo.co \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.