unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@purdue.edu>
To: guix-devel@gnu.org
Subject: Want help with writing package recipe
Date: Thu, 06 Mar 2014 18:03:47 -0500	[thread overview]
Message-ID: <5318FED3.8060305@purdue.edu> (raw)
In-Reply-To: <mailman.103.1394125227.23151.guix-devel@gnu.org>

     Hello,

     I'm trying to write a recipe to install GNU typist: 
http://www.gnu.org/software/gtypist/

     Just to be clear, one cannot install gtypist with "guix package -i 
gtypist", because guix does not currently have a recipe for gtypist.

     Anyway, I used guix download <path to tarball> to download the 
tarball for gtypist. It is stored locally on my machine in this path:
     /nix/store/lzxd537h0plmskizrldx6lmpyacl2d40-gtypist-2.9.4.tar.gz

     I used guix hash -f base32 to export the base32 hash, which is: 
i5q225g6twsg5egicgpt6ub7hn4m7pdzg56hwxx57jm4o4ns5fgq

     I've written a recipe for gtypist located here: 
http://pastebin.com/ysLHJUWg

     But now, I'm stuck. I'm not sure how to tell guix to run the 
recipe. Guix's documentation says that the command "guix build options 
package-or-derivation"
     will build the package into a binary that I can run on my machine. 
I can't say "guix build gtypist", because guix does not currently have a 
recipe to build gtypist,     and I can't say "guix build options 
/path/to/gtypist.dri", because there is not a derivation file on my 
machine for gtypist.

      What do I do next to build this package? How do I submit a patch 
when I get it working?

     Thanks,

     Joshua

       reply	other threads:[~2014-03-06 22:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.103.1394125227.23151.guix-devel@gnu.org>
2014-03-06 23:03 ` Joshua Branson [this message]
2014-03-07  9:26   ` Want help with writing package recipe Ludovic Courtès
2014-03-07  9:41   ` Nikita Karetnikov

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=5318FED3.8060305@purdue.edu \
    --to=jbranso@purdue.edu \
    --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).