From: Alex Griffin <a@ajgrf.com>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/3] gnu: Add ledger.
Date: Fri, 13 May 2016 16:05:57 -0500 [thread overview]
Message-ID: <1463173557.4042476.607311345.1A7582D5@webmail.messagingengine.com> (raw)
In-Reply-To: <87posp7oqa.fsf@gmail.com>
I don't know whether parallel builds should be enabled or disabled. My
initial thought was that it makes sense if it allows ledger to build on
more machines. On the other hand, the more general fix (one that will
also work on lots of other packages) is simply to allocate more swap on
those machines.
On Fri, May 13, 2016, at 02:16 PM, Alex Kost wrote:
> Overall, here is how I would write 'arguments' field of this package: [...]
Since I wrote this package largely by copying other packages I found,
I'm curious how I would ever learn some of this stuff. How do I know
which variables are available in different parts of the package
definition, and similar details? I could probably just continue diving
deeper into the source, but since it's guile I suspect there's some way
to explore interactively. I'm just not sure how; my REPL fu is weak.
--
Alex Griffin
next prev parent reply other threads:[~2016-05-13 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 18:38 [PATCH 2/3] gnu: Add ledger Alex Griffin
2016-05-07 19:20 ` Alex Griffin
2016-05-07 22:23 ` Leo Famulari
2016-05-08 2:10 ` Alex Griffin
2016-05-09 3:39 ` Leo Famulari
2016-05-09 20:23 ` Ludovic Courtès
2016-05-09 21:01 ` Leo Famulari
2016-05-12 3:28 ` Alex Griffin
2016-05-12 9:12 ` Alex Kost
2016-05-12 16:31 ` Alex Griffin
2016-05-12 19:03 ` Leo Famulari
2016-05-13 19:16 ` Alex Kost
2016-05-13 21:05 ` Alex Griffin [this message]
2016-05-14 2:49 ` Leo Famulari
2016-05-16 15:03 ` Alex Kost
2016-05-16 17:45 ` Christopher Allan Webber
2016-05-16 18:05 ` Efraim Flashner
2016-05-16 18:06 ` Leo Famulari
2016-05-16 18:45 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463173557.4042476.607311345.1A7582D5@webmail.messagingengine.com \
--to=a@ajgrf.com \
--cc=alezost@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.