From: Zachary Kanfer <zkanfer@gmail.com>
To: help-guix@gnu.org
Subject: Is there a beginner's guide to using Guix with Scheme files?
Date: Sun, 17 Apr 2016 00:15:12 -0400 [thread overview]
Message-ID: <CAFXT+RMOC4BbE+8zcR5Mcac+Gay-x6pJrrqniHfe41LgW9kqKQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]
I recently installed Guix, and I must admit I'm feeling somewhat lost. My
goal is to not run `guix package -i` manually, but have a scheme file with
my entire system configuration in it, and run `guix package -f
/path/to/that/file` to install the programs I want on my computer.
I think what I want to start with is here (
http://www.gnu.org/software/guix/manual/guix.html#Programming-Interface),
but I'm not sure. Looking at it is somewhat confusing, for a few reasons.
I'm going to list what I see when reading this in hopes that the
documentation can be improved.
1. It starts by discussing how to "define new packages". I would expect
that I would only want to *use* packages, and that this would be done by
the person adding the package to the software repository.
2. The example given looks like a very complicated way of installing a
simple package. There are many properties I don't care about when I'm
installing software (homepage, synopsis /and/ description), and things I
don't want to care about (arguments, inputs, build-system). To install a
package on the command line, it's something simple like "apt-get install
emacs". To use Guix, I have to write a 20-line program with a bunch of
settings?
3. It goes on to discuss importing other people's package definitions (
http://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-import).
But it doesn't say how to do this in a Scheme file. I want my setup to be
in a Scheme file, not in a bunch of commands I have to manually run.
4. It discusses running `guix build` to use the package definitions. This
appears to be different than `guix package -i`, but I'm at a loss to say
how.
Am I missing a useful page somewhere in the documentation? Do I have some
wrong assumptions about how Guix is used? Thanks for any help.
-Zachary
[-- Attachment #2: Type: text/html, Size: 2189 bytes --]
next reply other threads:[~2016-04-17 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 4:15 Zachary Kanfer [this message]
2016-04-17 13:52 ` Is there a beginner's guide to using Guix with Scheme files? Catonano
2016-04-18 4:06 ` Zachary Kanfer
2016-04-17 15:13 ` Ludovic Courtès
2016-04-18 4:19 ` Zachary Kanfer
2016-04-18 7:17 ` Ricardo Wurmus
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=CAFXT+RMOC4BbE+8zcR5Mcac+Gay-x6pJrrqniHfe41LgW9kqKQ@mail.gmail.com \
--to=zkanfer@gmail.com \
--cc=help-guix@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).