This file is indexed.

/usr/share/doc/ruby-popen4/README.rdoc is in ruby-popen4 0.1.4-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
== Description
POpen4 provides the Rubyist a single API across platforms for executing a
command in a child process with handles on stdout, stderr, stdin streams as well
as access to the process ID and exit status. It does very little other than to
provide an easy way to use either Ara Howard's Open4 library or the win32-popen3
library by Park Heesob and Daniel Berger depending on your platform and without
having to code around the slight differences in their APIs.

Consider this my first attempt at a response to
{Daniel's request}[http://groups.google.com/group/comp.lang.ruby/msg/44ba016610fa8878]
for a consensus on the API back in 2005.

It is my hope that this project will be shortly absorbed or replaced with a
better solution. POpen4 offers very little in the way of features or
flexibility, but it does work across platforms without extra coding.
== Notes
Rather than adopting either Open4's API or win32-open3's (they differ in several
respects, but most obviously in the order in which streams are passed to the
block) I am proposing a third API for couple of reasons. First, Open4 passes the
PID first and win32-open3 passes stdin neither of which seem to me to be the
streams we are most likely to use when we don't need all four. POpen4 passes
stdout and stderr first so that when the others are not required we can omit
them from the block. Second, I thought it best to break everybody's code rather
than to be a drop in replacement on one platform and be a surprise on another.
No surprises--it's a new API on either platform.

== Installation

   $ gem install POpen4 --source http://gemcutter.org

== Acknowledgements
Ara Howard, Park Heesob, Daniel Berger and others have done the real work. Many
thanks to them for the many hours they have poured into sharing their work with
the Ruby community at large.