From: swedebugia <swedebugia@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>, "Marius Bakke" <mbakke@fastmail.com>
Cc: 33279-done@debbugs.gnu.org
Subject: bug#33279: GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH on GuixSD
Date: Wed, 7 Nov 2018 18:08:35 +0100 [thread overview]
Message-ID: <110cf521-142c-63b7-e26f-4f751109520d@riseup.net> (raw)
In-Reply-To: <87ftwcu9h3.fsf_-_@gnu.org>
Hi
On 2018-11-07 17:40, Ludovic Courtès wrote:
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> swedebugia <swedebugia@riseup.net> writes:
> [...]
>
>>> Could we make all guile-* packages emit this suggestion?
>> This limitation is the same as <https://bugs.gnu.org/22138>.
> It’s actually a different issue here: the profile contains packages that
> provide share/guile/2.2, but the same profile doesn’t contain any
> package that “claims” share/guile/2.2. Thus, everything is working
> according to plan, so to speak.
>
> I understand this particular case is confusing though. It’s confusing
> because Guile is already installed, albeit in another profile.
>
> What we could do to avoid this confusion is pre-define GUILE_LOAD_PATH
> and GUILE_LOAD_COMPILED_PATH in /etc/profile, just like we do for
> INFOPATH et al.
Sounds good to me.
What I am after is lowering the bar for the user to learn and use guile
and readline seems like a pretty important component to avoid typing
everything over and over.
We want guix to be guile land and for guile land to be nice and welcome
out the box.
I therefore suggest also adding guile-readline to %base-packages if it
does not produce too much overhead.
Cheers
Swedebugia
prev parent reply other threads:[~2018-11-07 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 20:14 bug#33279: guile-readline: error: no code for module swedebugia
2018-11-06 11:36 ` Ludovic Courtès
2018-11-06 19:05 ` swedebugia
2018-11-06 20:14 ` Marius Bakke
2018-11-07 16:40 ` bug#33279: GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH on GuixSD Ludovic Courtès
2018-11-07 17:08 ` swedebugia [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=110cf521-142c-63b7-e26f-4f751109520d@riseup.net \
--to=swedebugia@riseup.net \
--cc=33279-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mbakke@fastmail.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.
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).