From: Christopher Baines <mail@cbaines.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: 38/40: gnu: Add ocaml-spawn.
Date: Wed, 06 Feb 2019 09:32:04 +0000 [thread overview]
Message-ID: <87sgx15kkr.fsf@cbaines.net> (raw)
In-Reply-To: <20190205213458.570F321585@vcs0.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
guix-commits@gnu.org writes:
> + (description
> + "Spawn is a small library exposing only one functionality: spawning sub-process.
> +
> +It has three main goals:
> +
> +@itemize
> +@item provide missing features of Unix.create_process such as providing a
> +working directory,
> +@item provide better errors when a system call fails in the
> +sub-process. For instance if a command is not found, you get a proper
> +@code{Unix.Unix_error} exception,
> +@item improve performances by using vfork when available. It is often
> +claimed that nowadays fork is as fast as vfork, however in practice
> +fork takes time proportional to the process memory while vfork is
> +constant time. In application using a lot of memory, vfork can be
> +thousands of times faster than fork.")
> + (license license:asl2.0)))
Just to let you know, I pushed a small change to the description
straight to master (as [1]) as I was having problems with guix package -s.
1: 1d5d0447d33fb50dc5ecb19ff94732ab935c6743
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next parent reply other threads:[~2019-02-06 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190205213451.20368.46156@vcs0.savannah.gnu.org>
[not found] ` <20190205213458.570F321585@vcs0.savannah.gnu.org>
2019-02-06 9:32 ` Christopher Baines [this message]
[not found] ` <20190205213457.C6CF421581@vcs0.savannah.gnu.org>
2019-02-06 9:46 ` 35/40: gnu: Add ocaml-splittable-random Christopher Baines
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=87sgx15kkr.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).