From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Ghc and profile creation bug
Date: Sun, 12 Apr 2015 21:00:31 +0200 [thread overview]
Message-ID: <20150412190031.GA4161@debian> (raw)
In-Reply-To: <87pp79v53h.fsf@gnu.org>
On Sun, Apr 12, 2015 at 03:38:58PM +0200, Ludovic Courtès wrote:
> While debugging it with Taylan on IRC, it occurred to us that
> guix/build-system/haskell.scm wasn’t getting installed, which is fixed
> by ce6fc7d. Can you confirm that this solves the problem?
It does, thanks a lot!
> Anyway, I recommend against using repeated “make install”, one reason
> being that there can be leftovers if you don’t run “make uninstall”
> beforehand.
It seems to be the good way of working in my "multi-user" setting. Why
should every user handle his own copy of guix? For instance, the daemon
needs to be installed in a system location to be started by the init system.
Anyway, "make install" needs to work.
> “guix pull” is meant to be a handy way to deal with updates.
Does this not interfere badly with git? I am running "make install" from my
latest stable master git branch, so that every user on the system has a recent
stable guix, with "stable" in the sense of a rolling release, not the latest
official relase. Then I use "./pre-inst-env" from my private branch in which
I am developing new packages.
Andreas
next prev parent reply other threads:[~2015-04-12 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 19:38 Ghc and profile creation bug Andreas Enge
2015-04-10 16:13 ` Ludovic Courtès
2015-04-12 13:38 ` Ludovic Courtès
2015-04-12 19:00 ` Andreas Enge [this message]
2015-04-12 20:56 ` guix pull Ludovic Courtès
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=20150412190031.GA4161@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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).