unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 27386@debbugs.gnu.org
Subject: bug#27386: offloading documentation and env
Date: Thu, 29 Jun 2017 13:50:58 +0200	[thread overview]
Message-ID: <87podnovvh.fsf@gnu.org> (raw)
In-Reply-To: <20170628223636.h3k24txegftwmlmk@abyayala> (ng0@infotropique.org's message of "Wed, 28 Jun 2017 22:36:36 +0000")

ng0 <ng0@infotropique.org> skribis:

> Ludovic Courtès transcribed 2.2K bytes:

[...]

>> > GUILE_LOAD_COMPILED_PATH="${GUILE_LOAD_COMPILED_PATH}:/run/current-system/profile/lib/guile/2.2/site-ccache:/run/current-system/profile/share/guile/site/2.2"
>> > GUILE_LOAD_PATH="${GUILE_LOAD_PATH}:/run/current-system/profile/share/guile/site/2.2"
>> 
>> The difference compared to /etc/skel/.bashrc is the last two lines,
>> right?
>
> Yes. And that I source ~/.guix-profile/etc/profile before those lines.
>
>> On my GuixSD installation they’re not needed because /etc/profile
>> sources /run/current-system/profile/etc/profile, which already defines
>> these two variables.
>
> Well this file is the same on both systems involved:
>
> user@abyayala ~$ cat /etc/profile

And does /run/current-system/profile/etc/profile define GUILE_LOAD_PATH?

Ludo'.

  reply	other threads:[~2017-06-29 11:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 17:05 bug#27386: offloading documentation and env ng0
2017-06-15 21:11 ` ng0
2017-06-15 22:19   ` ng0
2017-06-15 22:34     ` ng0
2017-06-26 19:56       ` Ludovic Courtès
2017-06-26 21:15         ` ng0
2017-06-27 13:39           ` Ludovic Courtès
2017-06-27 14:54             ` ng0
2017-06-27 19:38               ` Ludovic Courtès
2017-06-27 20:31                 ` ng0
2017-06-28  8:31                   ` Ludovic Courtès
2017-06-28 11:45                     ` ng0
2017-06-28 21:46                       ` Ludovic Courtès
2017-06-28 22:36                         ` ng0
2017-06-29 11:50                           ` Ludovic Courtès [this message]
2017-07-04 13:51                             ` Oleg Pykhalov
2017-07-04 15:43                               ` Oleg Pykhalov
2017-07-04 16:02                                 ` Oleg Pykhalov
2017-07-04 21:36                               ` Ludovic Courtès
2017-07-05 17:06                                 ` Oleg Pykhalov
2017-07-06  7:33                                   ` Ludovic Courtès
2017-07-06 13:15                                     ` Oleg Pykhalov
2017-07-07 10:00                                       ` Ludovic Courtès
     [not found]                                         ` <871spsginl.fsf@clover.i-did-not-set--mail-host-address--so-tickle-me>
2017-07-08 16:33                                           ` bug#27386: [SOLVED] " Ludovic Courtès
2017-09-28 19:40             ` Divan Santana
2017-09-28 19:44               ` Divan Santana
2017-09-29  7:49               ` Ludovic Courtès
2017-09-29 17:02                 ` Ricardo Wurmus
2017-09-29 19:35                   ` Divan Santana
2017-09-29 19:33                 ` Divan Santana

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=87podnovvh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27386@debbugs.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.
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).