unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Kete <kete@ninthfloor.org>
Cc: guix-devel@gnu.org
Subject: Re: Package Definition Place
Date: Fri, 3 Jan 2014 06:50:40 +0100	[thread overview]
Message-ID: <20140103055040.GA4180@intra> (raw)
In-Reply-To: <7377714.T8fEdJAmeB@knossos>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

On Thu, Jan 02, 2014 at 09:28:24PM -0500, Kete wrote:
     On Thursday, January 02, 2014 06:44:00 AM Nikita Karetnikov wrote:
     > $ git clone git://git.sv.gnu.org/guix.git
     > $ cd guix
     > $ ./bootstrap && ./configure --localstatedir=/nix/var && make && make check
     > 
     > (See ‘HACKING’ for more information.)
     > 
     > Then you could add a recipe (i.e., the definition of a package) to
     > ‘guix/gnu/packages’.  For instance, this commit [1] adds the elfutils
     > recipe to ‘gnu/packages/elf.scm’.
     > 
     > Did I forget to address anything?
     
     I copied my package definition to gnu/packages and added a line for it in gnu-
     system.am. Then, I ran './pre-inst-env guix build zsh' and got this output: 
     guix build: error: failed to connect to `/nix/var/nix/daemon-socket/socket': 
     No such file or directory

This would suggest that you haven't got a guix daemon running.

Install guix and set up the daemon as described in Chapter 2 of the GUIX manual.

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-01-03  5:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30  3:55 Package Definition Place Kete
2013-12-30  7:16 ` John Darrington
2013-12-31  0:37   ` Kete
2014-01-01 12:52     ` John Darrington
2014-01-01 16:05       ` Kete
     [not found] ` <1458111.8sUPPTkUlg@knossos>
     [not found]   ` <20140101160917.GA13487@intra>
2014-01-01 16:32     ` Kete
2014-01-01 16:50       ` John Darrington
2014-01-01 19:13         ` Kete
2014-01-01 19:55           ` John Darrington
2014-01-01 20:38             ` Kete
2014-01-01 22:30             ` Kete
2014-01-02  2:44               ` Nikita Karetnikov
2014-01-02  2:50                 ` Nikita Karetnikov
2014-01-02 10:06                   ` Kete
2014-01-02 14:58                     ` Nikita Karetnikov
2014-01-02 23:45                       ` Kete
2014-01-03  2:28                 ` Kete
2014-01-03  5:50                   ` John Darrington [this message]
2014-01-03 11:37                     ` Kete
2014-01-03 15:16                       ` Nikita Karetnikov
2014-01-03 15:19                       ` Ludovic Courtès
2014-01-04  1:10                         ` Kete
2014-01-04  7:15                           ` John Darrington
2014-01-04 21:21                             ` Kete
2014-01-04 22:25                               ` John Darrington
2014-01-05 18:21                               ` Ludovic Courtès
2014-01-04 11:47                           ` Ludovic Courtès
2014-01-04 21:31                             ` Kete
2014-01-05 17:57                               ` 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=20140103055040.GA4180@intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=kete@ninthfloor.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).