ruby-posix-spawn 0.3.11-1build1 source package in Ubuntu
Changelog
ruby-posix-spawn (0.3.11-1build1) xenial; urgency=medium * No-change rebuild to add ruby2.3 support. -- Matthias Klose <email address hidden> Sun, 13 Mar 2016 12:36:33 +0000
Upload details
- Uploaded by:
- Matthias Klose
- Uploaded to:
- Xenial
- Original maintainer:
- Debian Ruby Extras Maintainers
- Architectures:
- any
- Section:
- ruby
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| ruby-posix-spawn_0.3.11.orig.tar.gz | 25.8 KiB | 80d4309eb0668af9fe8969172f7eb102061a27ab408c47a0939835be5c02990b |
| ruby-posix-spawn_0.3.11-1build1.debian.tar.xz | 3.6 KiB | 180fd20fc65731eb47b7508a6251a32fabb8414e90a434d835fca54dbd809598 |
| ruby-posix-spawn_0.3.11-1build1.dsc | 2.1 KiB | f512dcbcf67baa90d8253bc00158783aa0779376437bbb6691c5cd635c5edb86 |
Available diffs
- diff from 0.3.11-1 (in Debian) to 0.3.11-1build1 (330 bytes)
Binary packages built by this source
- ruby-posix-spawn: Ruby Implementation of posix_spawn(2) for faster process spawning
The posix-spawn library aims to implement a subset of the Ruby 1.9
`Process::spawn` interface in a way that takes advantage of fast
process spawning interfaces when available and provides sane fallbacks
on systems that do not.
.
`fork(2)` calls slow down as the parent process uses more memory due to
the need to copy page tables. In many common uses of fork(), where it
is followed by one of the exec family of functions to spawn child
processes (`Kernel#system` ,`IO::popen` , `Process::spawn`, etc.), it's
possible to remove this overhead by using the use of special process
spawning interfaces (`posix_spawn()`, `vfork()`, etc.)
- ruby-posix-spawn-dbgsym: debug symbols for package ruby-posix-spawn
The posix-spawn library aims to implement a subset of the Ruby 1.9
`Process::spawn` interface in a way that takes advantage of fast
process spawning interfaces when available and provides sane fallbacks
on systems that do not.
.
`fork(2)` calls slow down as the parent process uses more memory due to
the need to copy page tables. In many common uses of fork(), where it
is followed by one of the exec family of functions to spawn child
processes (`Kernel#system` ,`IO::popen` , `Process::spawn`, etc.), it's
possible to remove this overhead by using the use of special process
spawning interfaces (`posix_spawn()`, `vfork()`, etc.)
