From: Matthew Jordan <matthewjordandevops@yandex.com>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] add go@1.6
Date: Thu, 28 Jul 2016 06:11:11 -0400 [thread overview]
Message-ID: <87bn1iysw0.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <1469667655.4000333.678845385.2261EF5D@webmail.messagingengine.com>
>> (version "1.6.2")
I'll update the version in an updated patch. Assuming no problems I'll
be happy to submit it.
>> (zero? (system* "sh" "all.bash")))))
>
> This seems to work, but I think it should just be `(zero? (system*
> "./all.bash"))`. It has a shebang, and expects bash, not sh.
Doesn't sh already handle picking the shell/interpretor? That's why I
put it there. sh or an sh compatible shell is usually the first to
start. Feel free to correct me if I'm wrong.
> If it doesn't cause any problems, we should delete pkg/bootstrap/* so
> that it doesn't retain any references to go@1.4. I think that would
> drastically reduce the size of its closure.
I'll look into this and get back to you.
> Also, I'm not sure I'm sold on splitting up into multiple outputs, but I
> haven't thought about it much and don't have a strong opinion. The
> "tests" output is only 5M and "doc" is only 10M, vs 270M for the default
> output.
This sounds like the beginning of a long conversation. Suffice to say
it's doesn't bother me either way. However I would rather change this
in later patch, if it has to be changed.
Respectuflly,
Matthew Jordan
next prev parent reply other threads:[~2016-07-28 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 23:54 [PATCH] add go@1.6 Matthew Jordan
2016-07-28 1:00 ` Alex Griffin
2016-07-28 10:11 ` Matthew Jordan [this message]
2016-07-28 11:25 ` Alex Griffin
2016-07-30 16:28 ` Matthew Jordan
2016-07-30 16:50 ` Alex Griffin
2016-07-31 22:55 ` Ludovic Courtès
2016-07-28 18:59 ` 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
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=87bn1iysw0.fsf@guixsd-mailerver.i-did-not-set--mail-host-address--so-tickle-me \
--to=matthewjordandevops@yandex.com \
--cc=a@ajgrf.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 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).