From: HiPhish <hiphish@posteo.de>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: guile-user@gnu.org
Subject: Re: Setting up Guile for use with Guix
Date: Sun, 26 Aug 2018 22:54:03 +0200 [thread overview]
Message-ID: <5292964.PsxyJmJGfY@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <61e604e8807205b1572cc2f63417f176@hypermove.net>
On Sonntag, 19. August 2018 22:41:30 CEST you wrote:
> It depends on how haunt package definition is written. Because of how guix
> works, you can use a program that uses guile without having 'guile' command
> available. Similarly, it makes it possible to run two programs at the same
> time that depends on different versions of the same library.. that's
something
> that is very difficult to do outside guix and nix. It's one of the
consequences
> of packaging is done. This leads to the point that in theory, you SHOULD
never
> install _libraries_ in your user profile ie. the regular / default profile
because
> no executable will use it. Default guix profile, SHOULD, I THINK, only
> contain data and executables.
I see. So if I want to work on some software that uses a particular library I
could install that library into a custom profile, enter that profile and do my
work.
> That is not a good example use of hacking on a guile project because
> guix is using
> it's own version of guile which might be different from the version of
> guile you
> installed in your profile... again because functional packaging. If you
> want to
> hack on guix follow the README that you can find in guix git repository
> at [1]
>
> [1] git clone https://git.savannah.gnu.org/git/guix.git
I did not know that Guix includes its own Guile, I thought it used the Guile
that's on the system.
parent reply other threads:[~2018-08-26 20:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <61e604e8807205b1572cc2f63417f176@hypermove.net>]
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=5292964.PsxyJmJGfY@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=amirouche@hypermove.net \
--cc=guile-user@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).