From: ludo@gnu.org (Ludovic Courtès)
To: manolis837@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add GNU Mach.
Date: Thu, 12 Jan 2017 15:11:31 +0100 [thread overview]
Message-ID: <87k2a04bcc.fsf@gnu.org> (raw)
In-Reply-To: <20170110173645.5806-2-manolis837@gmail.com> (manolis's message of "Tue, 10 Jan 2017 19:36:45 +0200")
manolis837@gmail.com skribis:
> From: Manolis Ragkousis <manolis837@gmail.com>
>
> * gnu/packages/hurd.scm (gnumach): New variable.
[...]
> + `(#:phases (modify-phases %standard-phases
> + (add-after 'install 'produce-image
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let* ((out (assoc-ref outputs "out"))
> + (boot (string-append out "/boot")))
> + (system* "make" "gnumach.gz")
> + (copy-file "gnumach.gz"
> + (string-append boot "/gnumach.gz"))))))))
Make sure the phase returns #t on success:
(and (zero? (system* "make" …))
(begin
(copy-file …)
#t))
> + (synopsis "Microkernel of the GNU system")
> + (description
> + "GNU Mach is the microkernel upon which a GNU Hurd system is based.")
> + (license gpl2+)))
Does it build both on GNU/Linux and GNU/Hurd?
We probably need a ‘supported-systems’ field to restrict to i686 and
x86_64(?) GNU/Hurd and possibly GNU/Linux.
OK with these changes, thank you!
Ludo’.
next prev parent reply other threads:[~2017-01-12 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:36 [PATCH 1/2] gnu: hurd: Add gnumach-source-url procedure manolis837
2017-01-10 17:36 ` [PATCH 2/2] gnu: Add GNU Mach manolis837
2017-01-12 14:11 ` Ludovic Courtès [this message]
2017-01-12 14:09 ` [PATCH 1/2] gnu: hurd: Add gnumach-source-url procedure Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2017-03-16 16:06 [PATCH 2/2] gnu: Add GNU Mach rennes
2017-03-19 16:21 ` Ludovic Courtès
2017-03-19 16:35 ` rennes
2017-03-21 10:27 ` Manolis Ragkousis
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=87k2a04bcc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=manolis837@gmail.com \
/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.