From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
zimoun <zimon.toutoune@gmail.com>,
Marius Bakke <mbakke@fastmail.com>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Appropriate way to use Guix API from a Guile program
Date: Fri, 22 May 2020 10:56:37 +0200 [thread overview]
Message-ID: <015b220bfe8fcca30854a53236b95bb6d6cc48af.camel@gmail.com> (raw)
In-Reply-To: <m1d06wza7a.fsf@khs-macbook.home>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
Hello,
On Fri, 2020-05-22 at 09:43 +0200, Konrad Hinsen wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
> > If you feel in an experimental mood, you can try the Konrad's patch
> > [1]. It sets up the PATH accordingly and hides all the internals.
>
> In particular it hides implementation details that are likely to
> change. A look at the path in
>
> ~/.config/guix/current/share/guile/site/3.0
>
> should be sufficient to suggest that not very long ago, this was
>
> ~/.config/guix/current/share/guile/site/2.2
>
> and scripts have no way to figure out which one of the two is
> appropriate on a given system.
I agree with all of this, and no doubt the ability to start Guile
scripts through Guix as ad-hoc ways to run scripts is useful.
I can't help but think that it would be really useful to have a way to
inject these load paths into the general user environment, in a way
similar to `guix package --search-paths', so that the currently pulled
guix can be just another guile library to be used on the system like
any other.
Would there be downsides to this?
Alex
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2020-05-22 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 21:38 Appropriate way to use Guix API from a Guile program sirgazil
2020-05-21 12:31 ` Efraim Flashner
2020-05-21 12:44 ` Marius Bakke
2020-05-21 13:25 ` sirgazil
2020-05-21 20:43 ` sirgazil
2020-05-21 20:52 ` Marius Bakke
2020-05-21 22:28 ` sirgazil
2020-05-21 23:02 ` zimoun
2020-05-22 7:43 ` Konrad Hinsen
2020-05-22 8:14 ` zimoun
2020-05-26 8:25 ` Konrad Hinsen
2020-05-26 16:00 ` Konrad Hinsen
2020-05-22 8:56 ` Alex Sassmannshausen [this message]
2020-05-22 14:28 ` sirgazil
2020-05-22 13:52 ` sirgazil
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=015b220bfe8fcca30854a53236b95bb6d6cc48af.camel@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=help-guix@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=mbakke@fastmail.com \
--cc=zimon.toutoune@gmail.com \
/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).