unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: guix import issue
Date: Sun, 14 Jun 2015 10:22:59 +0200	[thread overview]
Message-ID: <20150614082259.GA13129@thebird.nl> (raw)
In-Reply-To: <557D2B37.5080500@uq.edu.au>

On Sun, Jun 14, 2015 at 05:20:23PM +1000, Ben Woodcroft wrote:
> >One of the benefits of Guix is that you can press Ctrl-C any time
> >without consequences (I do it regularly).

> Thanks for the update. I knew this was true of installing packages,
> just wasn't sure about other operations.

It is not true for compiling Guix the first time from source. 

Once you are running guix itself to install/compile packages is a
transaction.  Sometimes annoyingly so because it keeps downloading and
building the same tarballs until completion.

> >This tells that your gnutls misses guile bindings (it may be that your
> >distro compiles gnutls with "--disable-guile" option).  I think it
> >should be fixed if you install gnutls with guix: "guix package -i
> >gnutls".
> This does indeed fix the error, and now I'm all set. Thanks.

Guile is everywhere, even GNU make:

  https://www.gnu.org/software/make/manual/html_node/Guile-Integration.html

Blessed is the man in whose spirit there is no guile ;).

Pj.

  reply	other threads:[~2015-06-14  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13  1:30 guix import issue Ben Woodcroft
2015-06-13 10:59 ` Ricardo Wurmus
2015-06-13 11:26   ` Ben Woodcroft
2015-06-13 13:14     ` Ludovic Courtès
2015-06-13 13:22       ` Ben Woodcroft
2015-06-13 14:46         ` Alex Kost
2015-06-14  7:20           ` Ben Woodcroft
2015-06-14  8:22             ` Pjotr Prins [this message]
2015-06-13 11:52   ` Pjotr Prins
2015-06-13 11:56     ` Ben Woodcroft

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=20150614082259.GA13129@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=alezost@gmail.com \
    --cc=b.woodcroft@uq.edu.au \
    --cc=guix-devel@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).