pkgsrc/devel/ruby-posix-spawn/distinfo

$NetBSD: distinfo,v 1.9 2020/09/13 16:04:28 taca Exp $

SHA1 (posix-spawn-0.3.15.gem) = 99ddcfacbc5417e20c3801fd9f4ce9376d3d09ea
RMD160 (posix-spawn-0.3.15.gem) = 977fd923ac0f76a67631c8f66a2e816279103851
SHA512 (posix-spawn-0.3.15.gem) = bdfecdbb0d470d23643de1c5b40c4f4b8b7f8970c14a2d3bd7c15e59d388b24857fb740c5c87573cbb6ac83483a29bf87f856a949a1fc014be8ad09e5cb2a9e7
Size (posix-spawn-0.3.15.gem) = 29696 bytes
devel/ruby-posix-spawn: update to 0.3.15 Update ruby-posix-spawn package to 0.3.15. 0.3.15 (2020-07-14) * Fix deprecated Object#=~ call. * Fix ambiguous argument warning. * Fix circular require warning. 2020-09-13 18:04:28 +02:00			$NetBSD: distinfo,v 1.9 2020/09/13 16:04:28 taca Exp $
Import ruby19-posix-spawn-0.3.6 as devel/ruby-posix-spawn. 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.) 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. 2011-08-21 06:57:36 +02:00
devel/ruby-posix-spawn: update to 0.3.15 Update ruby-posix-spawn package to 0.3.15. 0.3.15 (2020-07-14) * Fix deprecated Object#=~ call. * Fix ambiguous argument warning. * Fix circular require warning. 2020-09-13 18:04:28 +02:00			`SHA1 (posix-spawn-0.3.15.gem) = 99ddcfacbc5417e20c3801fd9f4ce9376d3d09ea`
			`RMD160 (posix-spawn-0.3.15.gem) = 977fd923ac0f76a67631c8f66a2e816279103851`
			`SHA512 (posix-spawn-0.3.15.gem) = bdfecdbb0d470d23643de1c5b40c4f4b8b7f8970c14a2d3bd7c15e59d388b24857fb740c5c87573cbb6ac83483a29bf87f856a949a1fc014be8ad09e5cb2a9e7`
			`Size (posix-spawn-0.3.15.gem) = 29696 bytes`