popenhs (empty) → 1.0.0
raw patch · 12 files changed
+997/−0 lines, 12 filesdep +basedep +directorydep +haskell98setup-changed
Dependencies added: base, directory, haskell98, unix
Files
- AUTHORS +5/−0
- ChangeLog +47/−0
- INSTALL +182/−0
- LICENSE +482/−0
- NEWS +13/−0
- README +29/−0
- Setup.hs +5/−0
- System/Posix/POpen.hs +104/−0
- TODO +1/−0
- index.html +45/−0
- popenhs.cabal +22/−0
- popenhs.spec.in +62/−0
+ AUTHORS view
@@ -0,0 +1,5 @@+Jens Petersen <juhp@01.246.ne.jp>+++Thanks to Uwe Schmidt <uwe@fh-wedel.de> for reporting the+problem that popen3 was hanging on closed input.
+ ChangeLog view
@@ -0,0 +1,47 @@+2002-01-25 Jens Petersen <juhp@01.246.ne.jp>++ * popenhs.spec.in: Tidied up. Use rpm macros.++ * index.html: Update for new release.++ * README: Update for 1.00.0.++ * NEWS: Add entries for 1.00.0 and 0.00.1.++ * Makefile.am (bin_SCRIPTS): Use PACKAGE.+ (pkglibdir): Use automake vars.+ (EXTRA_DIST): Add spec file.+ (rpm, web): New rules from hsclock. Use automake vars.++ * POpen.hs: Export popen and popenEnvDir now.+ Import hPutStr, hClose, fromJust, isJust and when.+ (popen): New wrapper function replacing popen2 and popen3 wrapper.+ Maybe takes additional arg for input string and no longer returns+ input handle.+ (popenEnvDir): New function replacing popenOutErr and+ popenInOutErr. Maybe takes additional arg for input string and no+ longer returns input handle. When there is input, create input+ pipe, write input string to it and close the pipe input handle.+ After forking, close pipe output fd in original process if there+ was input. This fixes the problem reported by Uwe <> that popen3+ was hanging on input from a pipe with closed input.+ (doTheBusiness): Maybe takes input fd, and no longer returns input+ handle. dupTo instead of mayDup2, since we always redirect. Only+ dup2 input when given input. Replace code after execFile to keep+ type-system happy with a error instead.+ (maybeDup2): Removed, since no longer needed.++ * configure.in: Up version to 1.00.0++2001-10-05 Jens Petersen <juhp@01.246.ne.jp>++ * popen.spec.in: new file, based on gtk+hs.spec.in++ * configure.in: use autoconf++ * Makefile.in: from Makefile++ * Makefile.am: use automake++ * acinclude.m4: was aclocal.m4+
+ INSTALL view
@@ -0,0 +1,182 @@+Basic Installation+==================++ These are generic installation instructions.++ The `configure' shell script attempts to guess correct values for+various system-dependent variables used during compilation. It uses+those values to create a `Makefile' in each directory of the package.+It may also create one or more `.h' files containing system-dependent+definitions. Finally, it creates a shell script `config.status' that+you can run in the future to recreate the current configuration, a file+`config.cache' that saves the results of its tests to speed up+reconfiguring, and a file `config.log' containing compiler output+(useful mainly for debugging `configure').++ If you need to do unusual things to compile the package, please try+to figure out how `configure' could check whether to do them, and mail+diffs or instructions to the address given in the `README' so they can+be considered for the next release. If at some point `config.cache'+contains results you don't want to keep, you may remove or edit it.++ The file `configure.in' is used to create `configure' by a program+called `autoconf'. You only need `configure.in' if you want to change+it or regenerate `configure' using a newer version of `autoconf'.++The simplest way to compile this package is:++ 1. `cd' to the directory containing the package's source code and type+ `./configure' to configure the package for your system. If you're+ using `csh' on an old version of System V, you might need to type+ `sh ./configure' instead to prevent `csh' from trying to execute+ `configure' itself.++ Running `configure' takes awhile. While running, it prints some+ messages telling which features it is checking for.++ 2. Type `make' to compile the package.++ 3. Optionally, type `make check' to run any self-tests that come with+ the package.++ 4. Type `make install' to install the programs and any data files and+ documentation.++ 5. You can remove the program binaries and object files from the+ source code directory by typing `make clean'. To also remove the+ files that `configure' created (so you can compile the package for+ a different kind of computer), type `make distclean'. There is+ also a `make maintainer-clean' target, but that is intended mainly+ for the package's developers. If you use it, you may have to get+ all sorts of other programs in order to regenerate files that came+ with the distribution.++Compilers and Options+=====================++ Some systems require unusual options for compilation or linking that+the `configure' script does not know about. You can give `configure'+initial values for variables by setting them in the environment. Using+a Bourne-compatible shell, you can do that on the command line like+this:+ CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure++Or on systems that have the `env' program, you can do it like this:+ env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure++Compiling For Multiple Architectures+====================================++ You can compile the package for more than one kind of computer at the+same time, by placing the object files for each architecture in their+own directory. To do this, you must use a version of `make' that+supports the `VPATH' variable, such as GNU `make'. `cd' to the+directory where you want the object files and executables to go and run+the `configure' script. `configure' automatically checks for the+source code in the directory that `configure' is in and in `..'.++ If you have to use a `make' that does not supports the `VPATH'+variable, you have to compile the package for one architecture at a time+in the source code directory. After you have installed the package for+one architecture, use `make distclean' before reconfiguring for another+architecture.++Installation Names+==================++ By default, `make install' will install the package's files in+`/usr/local/bin', `/usr/local/man', etc. You can specify an+installation prefix other than `/usr/local' by giving `configure' the+option `--prefix=PATH'.++ You can specify separate installation prefixes for+architecture-specific files and architecture-independent files. If you+give `configure' the option `--exec-prefix=PATH', the package will use+PATH as the prefix for installing programs and libraries.+Documentation and other data files will still use the regular prefix.++ In addition, if you use an unusual directory layout you can give+options like `--bindir=PATH' to specify different values for particular+kinds of files. Run `configure --help' for a list of the directories+you can set and what kinds of files go in them.++ If the package supports it, you can cause programs to be installed+with an extra prefix or suffix on their names by giving `configure' the+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.++Optional Features+=================++ Some packages pay attention to `--enable-FEATURE' options to+`configure', where FEATURE indicates an optional part of the package.+They may also pay attention to `--with-PACKAGE' options, where PACKAGE+is something like `gnu-as' or `x' (for the X Window System). The+`README' should mention any `--enable-' and `--with-' options that the+package recognizes.++ For packages that use the X Window System, `configure' can usually+find the X include and library files automatically, but if it doesn't,+you can use the `configure' options `--x-includes=DIR' and+`--x-libraries=DIR' to specify their locations.++Specifying the System Type+==========================++ There may be some features `configure' can not figure out+automatically, but needs to determine by the type of host the package+will run on. Usually `configure' can figure that out, but if it prints+a message saying it can not guess the host type, give it the+`--host=TYPE' option. TYPE can either be a short name for the system+type, such as `sun4', or a canonical name with three fields:+ CPU-COMPANY-SYSTEM++See the file `config.sub' for the possible values of each field. If+`config.sub' isn't included in this package, then this package doesn't+need to know the host type.++ If you are building compiler tools for cross-compiling, you can also+use the `--target=TYPE' option to select the type of system they will+produce code for and the `--build=TYPE' option to select the type of+system on which you are compiling the package.++Sharing Defaults+================++ If you want to set default values for `configure' scripts to share,+you can create a site shell script called `config.site' that gives+default values for variables like `CC', `cache_file', and `prefix'.+`configure' looks for `PREFIX/share/config.site' if it exists, then+`PREFIX/etc/config.site' if it exists. Or, you can set the+`CONFIG_SITE' environment variable to the location of the site script.+A warning: not all `configure' scripts look for a site script.++Operation Controls+==================++ `configure' recognizes the following options to control how it+operates.++`--cache-file=FILE'+ Use and save the results of the tests in FILE instead of+ `./config.cache'. Set FILE to `/dev/null' to disable caching, for+ debugging `configure'.++`--help'+ Print a summary of the options to `configure', and exit.++`--quiet'+`--silent'+`-q'+ Do not print messages saying which checks are being made. To+ suppress all normal output, redirect it to `/dev/null' (any error+ messages will still be shown).++`--srcdir=DIR'+ Look for the package's source code in directory DIR. Usually+ `configure' can determine that directory automatically.++`--version'+ Print the version of Autoconf used to generate the `configure'+ script, and exit.++`configure' also accepts some other, not widely useful, options.
+ LICENSE view
@@ -0,0 +1,482 @@+ GNU LIBRARY GENERAL PUBLIC LICENSE+ Version 2, June 1991++ Copyright (C) 1991 Free Software Foundation, Inc.+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA+ Everyone is permitted to copy and distribute verbatim copies+ of this license document, but changing it is not allowed.++[This is the first released version of the library GPL. It is+ numbered 2 because it goes with version 2 of the ordinary GPL.]++ Preamble++ The licenses for most software are designed to take away your+freedom to share and change it. By contrast, the GNU General Public+Licenses are intended to guarantee your freedom to share and change+free software--to make sure the software is free for all its users.++ This license, the Library General Public License, applies to some+specially designated Free Software Foundation software, and to any+other libraries whose authors decide to use it. You can use it for+your libraries, too.++ When we speak of free software, we are referring to freedom, not+price. Our General Public Licenses are designed to make sure that you+have the freedom to distribute copies of free software (and charge for+this service if you wish), that you receive source code or can get it+if you want it, that you can change the software or use pieces of it+in new free programs; and that you know you can do these things.++ To protect your rights, we need to make restrictions that forbid+anyone to deny you these rights or to ask you to surrender the rights.+These restrictions translate to certain responsibilities for you if+you distribute copies of the library, or if you modify it.++ For example, if you distribute copies of the library, whether gratis+or for a fee, you must give the recipients all the rights that we gave+you. You must make sure that they, too, receive or can get the source+code. If you link a program with the library, you must provide+complete object files to the recipients so that they can relink them+with the library, after making changes to the library and recompiling+it. And you must show them these terms so they know their rights.++ Our method of protecting your rights has two steps: (1) copyright+the library, and (2) offer you this license which gives you legal+permission to copy, distribute and/or modify the library.++ Also, for each distributor's protection, we want to make certain+that everyone understands that there is no warranty for this free+library. If the library is modified by someone else and passed on, we+want its recipients to know that what they have is not the original+version, so that any problems introduced by others will not reflect on+the original authors' reputations.++ Finally, any free program is threatened constantly by software+patents. We wish to avoid the danger that companies distributing free+software will individually obtain patent licenses, thus in effect+transforming the program into proprietary software. To prevent this,+we have made it clear that any patent must be licensed for everyone's+free use or not licensed at all.++ Most GNU software, including some libraries, is covered by the ordinary+GNU General Public License, which was designed for utility programs. This+license, the GNU Library General Public License, applies to certain+designated libraries. This license is quite different from the ordinary+one; be sure to read it in full, and don't assume that anything in it is+the same as in the ordinary license.++ The reason we have a separate public license for some libraries is that+they blur the distinction we usually make between modifying or adding to a+program and simply using it. Linking a program with a library, without+changing the library, is in some sense simply using the library, and is+analogous to running a utility program or application program. However, in+a textual and legal sense, the linked executable is a combined work, a+derivative of the original library, and the ordinary General Public License+treats it as such.++ Because of this blurred distinction, using the ordinary General+Public License for libraries did not effectively promote software+sharing, because most developers did not use the libraries. We+concluded that weaker conditions might promote sharing better.++ However, unrestricted linking of non-free programs would deprive the+users of those programs of all benefit from the free status of the+libraries themselves. This Library General Public License is intended to+permit developers of non-free programs to use free libraries, while+preserving your freedom as a user of such programs to change the free+libraries that are incorporated in them. (We have not seen how to achieve+this as regards changes in header files, but we have achieved it as regards+changes in the actual functions of the Library.) The hope is that this+will lead to faster development of free libraries.++ The precise terms and conditions for copying, distribution and+modification follow. Pay close attention to the difference between a+"work based on the library" and a "work that uses the library". The+former contains code derived from the library, while the latter only+works together with the library.++ Note that it is possible for a library to be covered by the ordinary+General Public License rather than by this special one.++ GNU LIBRARY GENERAL PUBLIC LICENSE+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION++ 0. This License Agreement applies to any software library which+contains a notice placed by the copyright holder or other authorized+party saying it may be distributed under the terms of this Library+General Public License (also called "this License"). Each licensee is+addressed as "you".++ A "library" means a collection of software functions and/or data+prepared so as to be conveniently linked with application programs+(which use some of those functions and data) to form executables.++ The "Library", below, refers to any such software library or work+which has been distributed under these terms. A "work based on the+Library" means either the Library or any derivative work under+copyright law: that is to say, a work containing the Library or a+portion of it, either verbatim or with modifications and/or translated+straightforwardly into another language. (Hereinafter, translation is+included without limitation in the term "modification".)++ "Source code" for a work means the preferred form of the work for+making modifications to it. For a library, complete source code means+all the source code for all modules it contains, plus any associated+interface definition files, plus the scripts used to control compilation+and installation of the library.++ Activities other than copying, distribution and modification are not+covered by this License; they are outside its scope. The act of+running a program using the Library is not restricted, and output from+such a program is covered only if its contents constitute a work based+on the Library (independent of the use of the Library in a tool for+writing it). Whether that is true depends on what the Library does+and what the program that uses the Library does.+ + 1. You may copy and distribute verbatim copies of the Library's+complete source code as you receive it, in any medium, provided that+you conspicuously and appropriately publish on each copy an+appropriate copyright notice and disclaimer of warranty; keep intact+all the notices that refer to this License and to the absence of any+warranty; and distribute a copy of this License along with the+Library.++ You may charge a fee for the physical act of transferring a copy,+and you may at your option offer warranty protection in exchange for a+fee.++ 2. You may modify your copy or copies of the Library or any portion+of it, thus forming a work based on the Library, and copy and+distribute such modifications or work under the terms of Section 1+above, provided that you also meet all of these conditions:++ a) The modified work must itself be a software library.++ b) You must cause the files modified to carry prominent notices+ stating that you changed the files and the date of any change.++ c) You must cause the whole of the work to be licensed at no+ charge to all third parties under the terms of this License.++ d) If a facility in the modified Library refers to a function or a+ table of data to be supplied by an application program that uses+ the facility, other than as an argument passed when the facility+ is invoked, then you must make a good faith effort to ensure that,+ in the event an application does not supply such function or+ table, the facility still operates, and performs whatever part of+ its purpose remains meaningful.++ (For example, a function in a library to compute square roots has+ a purpose that is entirely well-defined independent of the+ application. Therefore, Subsection 2d requires that any+ application-supplied function or table used by this function must+ be optional: if the application does not supply it, the square+ root function must still compute square roots.)++These requirements apply to the modified work as a whole. If+identifiable sections of that work are not derived from the Library,+and can be reasonably considered independent and separate works in+themselves, then this License, and its terms, do not apply to those+sections when you distribute them as separate works. But when you+distribute the same sections as part of a whole which is a work based+on the Library, the distribution of the whole must be on the terms of+this License, whose permissions for other licensees extend to the+entire whole, and thus to each and every part regardless of who wrote+it.++Thus, it is not the intent of this section to claim rights or contest+your rights to work written entirely by you; rather, the intent is to+exercise the right to control the distribution of derivative or+collective works based on the Library.++In addition, mere aggregation of another work not based on the Library+with the Library (or with a work based on the Library) on a volume of+a storage or distribution medium does not bring the other work under+the scope of this License.++ 3. You may opt to apply the terms of the ordinary GNU General Public+License instead of this License to a given copy of the Library. To do+this, you must alter all the notices that refer to this License, so+that they refer to the ordinary GNU General Public License, version 2,+instead of to this License. (If a newer version than version 2 of the+ordinary GNU General Public License has appeared, then you can specify+that version instead if you wish.) Do not make any other change in+these notices.++ Once this change is made in a given copy, it is irreversible for+that copy, so the ordinary GNU General Public License applies to all+subsequent copies and derivative works made from that copy.++ This option is useful when you wish to copy part of the code of+the Library into a program that is not a library.++ 4. You may copy and distribute the Library (or a portion or+derivative of it, under Section 2) in object code or executable form+under the terms of Sections 1 and 2 above provided that you accompany+it with the complete corresponding machine-readable source code, which+must be distributed under the terms of Sections 1 and 2 above on a+medium customarily used for software interchange.++ If distribution of object code is made by offering access to copy+from a designated place, then offering equivalent access to copy the+source code from the same place satisfies the requirement to+distribute the source code, even though third parties are not+compelled to copy the source along with the object code.++ 5. A program that contains no derivative of any portion of the+Library, but is designed to work with the Library by being compiled or+linked with it, is called a "work that uses the Library". Such a+work, in isolation, is not a derivative work of the Library, and+therefore falls outside the scope of this License.++ However, linking a "work that uses the Library" with the Library+creates an executable that is a derivative of the Library (because it+contains portions of the Library), rather than a "work that uses the+library". The executable is therefore covered by this License.+Section 6 states terms for distribution of such executables.++ When a "work that uses the Library" uses material from a header file+that is part of the Library, the object code for the work may be a+derivative work of the Library even though the source code is not.+Whether this is true is especially significant if the work can be+linked without the Library, or if the work is itself a library. The+threshold for this to be true is not precisely defined by law.++ If such an object file uses only numerical parameters, data+structure layouts and accessors, and small macros and small inline+functions (ten lines or less in length), then the use of the object+file is unrestricted, regardless of whether it is legally a derivative+work. (Executables containing this object code plus portions of the+Library will still fall under Section 6.)++ Otherwise, if the work is a derivative of the Library, you may+distribute the object code for the work under the terms of Section 6.+Any executables containing that work also fall under Section 6,+whether or not they are linked directly with the Library itself.++ 6. As an exception to the Sections above, you may also compile or+link a "work that uses the Library" with the Library to produce a+work containing portions of the Library, and distribute that work+under terms of your choice, provided that the terms permit+modification of the work for the customer's own use and reverse+engineering for debugging such modifications.++ You must give prominent notice with each copy of the work that the+Library is used in it and that the Library and its use are covered by+this License. You must supply a copy of this License. If the work+during execution displays copyright notices, you must include the+copyright notice for the Library among them, as well as a reference+directing the user to the copy of this License. Also, you must do one+of these things:++ a) Accompany the work with the complete corresponding+ machine-readable source code for the Library including whatever+ changes were used in the work (which must be distributed under+ Sections 1 and 2 above); and, if the work is an executable linked+ with the Library, with the complete machine-readable "work that+ uses the Library", as object code and/or source code, so that the+ user can modify the Library and then relink to produce a modified+ executable containing the modified Library. (It is understood+ that the user who changes the contents of definitions files in the+ Library will not necessarily be able to recompile the application+ to use the modified definitions.)++ b) Accompany the work with a written offer, valid for at+ least three years, to give the same user the materials+ specified in Subsection 6a, above, for a charge no more+ than the cost of performing this distribution.++ c) If distribution of the work is made by offering access to copy+ from a designated place, offer equivalent access to copy the above+ specified materials from the same place.++ d) Verify that the user has already received a copy of these+ materials or that you have already sent this user a copy.++ For an executable, the required form of the "work that uses the+Library" must include any data and utility programs needed for+reproducing the executable from it. However, as a special exception,+the source code distributed need not include anything that is normally+distributed (in either source or binary form) with the major+components (compiler, kernel, and so on) of the operating system on+which the executable runs, unless that component itself accompanies+the executable.++ It may happen that this requirement contradicts the license+restrictions of other proprietary libraries that do not normally+accompany the operating system. Such a contradiction means you cannot+use both them and the Library together in an executable that you+distribute.++ 7. You may place library facilities that are a work based on the+Library side-by-side in a single library together with other library+facilities not covered by this License, and distribute such a combined+library, provided that the separate distribution of the work based on+the Library and of the other library facilities is otherwise+permitted, and provided that you do these two things:++ a) Accompany the combined library with a copy of the same work+ based on the Library, uncombined with any other library+ facilities. This must be distributed under the terms of the+ Sections above.++ b) Give prominent notice with the combined library of the fact+ that part of it is a work based on the Library, and explaining+ where to find the accompanying uncombined form of the same work.++ 8. You may not copy, modify, sublicense, link with, or distribute+the Library except as expressly provided under this License. Any+attempt otherwise to copy, modify, sublicense, link with, or+distribute the Library is void, and will automatically terminate your+rights under this License. However, parties who have received copies,+or rights, from you under this License will not have their licenses+terminated so long as such parties remain in full compliance.++ 9. You are not required to accept this License, since you have not+signed it. However, nothing else grants you permission to modify or+distribute the Library or its derivative works. These actions are+prohibited by law if you do not accept this License. Therefore, by+modifying or distributing the Library (or any work based on the+Library), you indicate your acceptance of this License to do so, and+all its terms and conditions for copying, distributing or modifying+the Library or works based on it.++ 10. Each time you redistribute the Library (or any work based on the+Library), the recipient automatically receives a license from the+original licensor to copy, distribute, link with or modify the Library+subject to these terms and conditions. You may not impose any further+restrictions on the recipients' exercise of the rights granted herein.+You are not responsible for enforcing compliance by third parties to+this License.++ 11. If, as a consequence of a court judgment or allegation of patent+infringement or for any other reason (not limited to patent issues),+conditions are imposed on you (whether by court order, agreement or+otherwise) that contradict the conditions of this License, they do not+excuse you from the conditions of this License. If you cannot+distribute so as to satisfy simultaneously your obligations under this+License and any other pertinent obligations, then as a consequence you+may not distribute the Library at all. For example, if a patent+license would not permit royalty-free redistribution of the Library by+all those who receive copies directly or indirectly through you, then+the only way you could satisfy both it and this License would be to+refrain entirely from distribution of the Library.++If any portion of this section is held invalid or unenforceable under any+particular circumstance, the balance of the section is intended to apply,+and the section as a whole is intended to apply in other circumstances.++It is not the purpose of this section to induce you to infringe any+patents or other property right claims or to contest validity of any+such claims; this section has the sole purpose of protecting the+integrity of the free software distribution system which is+implemented by public license practices. Many people have made+generous contributions to the wide range of software distributed+through that system in reliance on consistent application of that+system; it is up to the author/donor to decide if he or she is willing+to distribute software through any other system and a licensee cannot+impose that choice.++This section is intended to make thoroughly clear what is believed to+be a consequence of the rest of this License.++ 12. If the distribution and/or use of the Library is restricted in+certain countries either by patents or by copyrighted interfaces, the+original copyright holder who places the Library under this License may add+an explicit geographical distribution limitation excluding those countries,+so that distribution is permitted only in or among countries not thus+excluded. In such case, this License incorporates the limitation as if+written in the body of this License.++ 13. The Free Software Foundation may publish revised and/or new+versions of the Library General Public License from time to time.+Such new versions will be similar in spirit to the present version,+but may differ in detail to address new problems or concerns.++Each version is given a distinguishing version number. If the Library+specifies a version number of this License which applies to it and+"any later version", you have the option of following the terms and+conditions either of that version or of any later version published by+the Free Software Foundation. If the Library does not specify a+license version number, you may choose any version ever published by+the Free Software Foundation.++ 14. If you wish to incorporate parts of the Library into other free+programs whose distribution conditions are incompatible with these,+write to the author to ask for permission. For software which is+copyrighted by the Free Software Foundation, write to the Free+Software Foundation; we sometimes make exceptions for this. Our+decision will be guided by the two goals of preserving the free status+of all derivatives of our free software and of promoting the sharing+and reuse of software generally.++ NO WARRANTY++ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.++ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH+DAMAGES.++ END OF TERMS AND CONDITIONS++ How to Apply These Terms to Your New Libraries++ If you develop a new library, and you want it to be of the greatest+possible use to the public, we recommend making it free software that+everyone can redistribute and change. You can do so by permitting+redistribution under these terms (or, alternatively, under the terms of the+ordinary General Public License).++ To apply these terms, attach the following notices to the library. It is+safest to attach them to the start of each source file to most effectively+convey the exclusion of warranty; and each file should have at least the+"copyright" line and a pointer to where the full notice is found.++ <one line to give the library's name and a brief idea of what it does.>+ Copyright (C) <year> <name of author>++ This library is free software; you can redistribute it and/or+ modify it under the terms of the GNU Library General Public+ License as published by the Free Software Foundation; either+ version 2 of the License, or (at your option) any later version.++ This library is distributed in the hope that it will be useful,+ but WITHOUT ANY WARRANTY; without even the implied warranty of+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU+ Library General Public License for more details.++ You should have received a copy of the GNU Library General Public+ License along with this library; if not, write to the + Free Software Foundation, Inc., 59 Temple Place - Suite 330, + Boston, MA 02111-1307 USA.++Also add information on how to contact you by electronic and paper mail.++You should also get your employer (if you work as a programmer) or your+school, if any, to sign a "copyright disclaimer" for the library, if+necessary. Here is a sample; alter the names:++ Yoyodyne, Inc., hereby disclaims all copyright interest in the+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.++ <signature of Ty Coon>, 1 April 1990+ Ty Coon, President of Vice++That's all there is to it!
+ NEWS view
@@ -0,0 +1,13 @@+New in 1.00.0+* API changed slightly.+* fixed problem that popen3 was hanging on closed input.+* popen which replaces popen2 and popen3 should now do the right thing.++New in 0.00.1+* fixed spec file++New in 0.00+* first release!+* provide popen2 and popen3+* uses automake and autoconf+* spec file
+ README view
@@ -0,0 +1,29 @@+popenhs is a small Haskell library that provides a+convenient way of sending string input to a subprocess and+reading output lazily. The code is based on runProcess from+the hslibs posix library. (It is also an example of how to+use automake in haskell packages.)++It provides two functions popen and popenEnvDir.++* popen gives lazy output and error streams from a+subprocess command, and optionally can direct input from a+string to the process.++* popenEnvDir in addition lets specify environment and+directory in which to run the subprocess command.+++Building should be straightforward. See the generic INSTALL+file and "./configure --help" for more details.++* run "./configure"++* then "make"++* and "make install"++For applications using popenhs, a helper program+"popenhs-config" is provided that can be used in Makefile's+for example to get the correct compile and link options.+"popenhs-config --help" gives more information.
+ Setup.hs view
@@ -0,0 +1,5 @@+#!/usr/bin/runhaskell++import Distribution.Simple++main = defaultMainWithHooks defaultUserHooks
+ System/Posix/POpen.hs view
@@ -0,0 +1,104 @@+-- popen-like library+--+-- Author : Jens-Ulrik Petersen+-- Created: 16 August 2001+--+-- Version: $Revision: 1.5 $ from $Date: 2001/10/17 07:30:53 $+--+-- Copyright (c) 2001 Jens-Ulrik Holger Petersen+-- (c) The GRASP/AQUA Project, Glasgow University, 1995-1996+--+-- This library is free software; you can redistribute it and/or+-- modify it under the terms of the GNU Library General Public+-- License as published by the Free Software Foundation; either+-- version 2 of the License, or (at your option) any later version.+--+-- This library is distributed in the hope that it will be useful,+-- but WITHOUT ANY WARRANTY; without even the implied warranty of+-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU+-- Library General Public License for more details.+--+-- Description+--++-- This code is based on runProcess from the hslibs posix+-- library, but internally it uses file descriptors instead+-- of handles and returns the output and error streams+-- lazily as strings as well as the pid of forked process,+-- instead of just IO ().++module System.Posix.POpen (popen, popenEnvDir)+where++import System.Posix.Types (Fd(), ProcessID())+import System.Posix.IO (createPipe, fdToHandle, closeFd, dupTo, stdInput, stdOutput, stdError)+-- import Control.Concurrent (forkIO)+import System.Posix.Process (executeFile)+import System.Directory (setCurrentDirectory)+import System.IO (hGetContents, hPutStr, hClose)+import Data.Maybe (fromJust, isJust)+import Control.Monad (when)++popen :: FilePath -- Command+ -> [String] -- Arguments+ -> Maybe String -- Input+ -> IO (String, String, ProcessID) -- (stdout, stderr, pid)+popen path args inpt =+ popenEnvDir path args inpt Nothing Nothing++popenEnvDir :: FilePath -- Command+ -> [String] -- Arguments+ -> Maybe String -- Input+ -> Maybe [(String, String)] -- Environment+ -> Maybe FilePath -- Working directory+ -- (stdin, stdout, stderr, pid)+ -> IO (String, String, ProcessID)+popenEnvDir path args inpt env dir =+ do+ inr <- if (isJust inpt) then+ do+ (inr', inw) <- createPipe+ hin <- fdToHandle inw+ hPutStr hin $ fromJust inpt+ hClose hin+ return $ Just inr'+ else+ return Nothing+ (outr, outw) <- createPipe+ (errr, errw) <- createPipe+-- pid <- forkIO+ p <- doTheBusiness inr outw errw+ do+ -- close other end of pipes in here+ when (isJust inr) $+ closeFd $ fromJust inr+ closeFd outw+ closeFd errw+ hout <- fdToHandle outr+ outstrm <- hGetContents hout+ herr <- fdToHandle errr+ errstrm <- hGetContents herr+ return (outstrm, errstrm, (third p))+ where+ third (_,_,c) = c+ doTheBusiness ::+ Maybe Fd -- stdin+ -> Fd -- stdout+ -> Fd -- stderr+ -> IO (String, String, ProcessID) -- (stdout, stderr)+ doTheBusiness inr outw errw =+ do+ maybeChangeWorkingDirectory dir+ when (isJust inr) $+ dupTo (fromJust inr) stdInput >> return ()+ dupTo outw stdOutput+ dupTo errw stdError+ executeFile path True args env+ -- for typing, should never actually run+ error "executeFile failed!"++maybeChangeWorkingDirectory :: Maybe FilePath -> IO ()+maybeChangeWorkingDirectory dir =+ case dir of+ Nothing -> return ()+ Just x -> setCurrentDirectory x
+ TODO view
@@ -0,0 +1,1 @@+All ears for feature requests and comments!
+ index.html view
@@ -0,0 +1,45 @@+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">+ <head>+ <title>popenhs</title>+ <style type="text/css">+ body {+ color: black;+ background: white;+ }+ </style>+ </head>+ + <body>+ <h1>popenhs</h1>++ <h2>Description</h2>+ <p>popenhs is a popen-like library for Haskell. It provides a convenient way of sending string input to a subprocess and reading output from it lazily. It requires the Posix module and has been tested under ghc5 so far.</p>++ <h2>Releases</h2>+ <p><b>2002-01-25</b> popenhs-1.00.0 released: <a href="popenhs-1.00.0.tar.gz">source tarball</a>, <a href="popenhs-1.00.0-1.i386.rpm">i386 rpm</a> (for ghc-5.02.2), <a href="popenhs-1.00.0-1.src.rpm">source rpm</a>, and <a href="ChangeLog">ChangeLog</a>.+ <ul>+ <li>popen replaces popen2 and popen3</li>+ <li>takes maybe an input string arg (instead of returning an input handle like popen3 did)</li>+ <li>no longer hangs on closed input pipe</li>+ </ul>+ </p>+ <p><b>2001-10-18</b> popenhs-0.00.1 released: <a href="popenhs-0.00.1.tar.gz">source tarball</a>, <a href="popenhs-0.00.1-1.i386.rpm">i386 rpm</a> and <a href="popenhs-0.00.1-1.src.rpm">source rpm</a>+ <ul>+ <li>added defattr to spec file</li>+ </ul>+ </p>+ <p><b>2001-10-17</b> popenhs-0.00 released: <a href="popenhs-0.00.tar.gz">source tarball</a>, <a href="popenhs-0.00-1.i386.rpm">i386 rpm</a> and <a href="popenhs-0.00-1.src.rpm">source rpm</a>+ <ul>+ <li>initial release</li>+ </ul>+ </p>++ <hr />+ <address><a href="mailto:juhp@01.246.ne.jp">Jens-Ulrik Petersen</a></address>+<!-- Created: Mon Feb 19 07:32:00 JST 2001 -->+<!-- hhmts start -->+Last modified: Fri Jan 25 15:40:48 JST 2002+<!-- hhmts end -->+ </body>+</html>
+ popenhs.cabal view
@@ -0,0 +1,22 @@+name: popenhs+version: 1.0.0+synopsis: popenhs is a popen-like library for Haskell.+description: It provides a convenient way of sending string input to+ a subprocess and reading output from it lazily. It requires+ the Posix module and has been tested under ghc5 so far.+category: System+license: GPL+license-file: LICENSE+author: Jens-Ulrik Petersen+maintainer: Jens-Ulrik Petersen <juhp@01.246.ne.jp>+homepage: http://www.haskell.org/~petersen/haskell/popenhs/+build-type: Simple+Cabal-Version: >= 1.2+data-files: AUTHORS, INSTALL, NEWS, README, TODO, ChangeLog, index.html, popenhs.spec.in++Library+ exposed-modules: System.Posix.POpen+ build-depends: base, haskell98, directory, unix++ ghc-options: -O2 -Wall -optl-Wl,-s+ ghc-prof-options: -prof -auto-all
+ popenhs.spec.in view
@@ -0,0 +1,62 @@+# RPM spec file for popenhs+#+# Copyright 2001 Jens-Ulrik Petersen <juhp@01.246.ne.jp>++Name: @PACKAGE@+Version: @VERSION@+Release: @RELEASE@+License: LGPL+Summary: A popen-like library for Haskell+Group: Development/Libraries+Source: http://www.01.246.ne.jp/~juhp/haskell/%{name}/%{name}-%{version}.tar.gz+URL: http://www.01.246.ne.jp/~juhp/haskell/%{name}/+BuildRoot: /var/tmp/%{name}-%{version}-%{release}-root+Packager: Jens-Ulrik Petersen <juhp@01.246.ne.jp>+Requires: haskell+Provides: %{name}++%description+A popen-like library for Haskell, providing lazy output from subprocesses.++Haskell 98 is "the" standard lazy functional programming language.+More info and the language definition are at http://www.haskell.org/.+++%changelog+* Fri Jan 25 2002 Jens Petersen <juhp@01.246.ne.jp> 1.00.0-1+- new version: API changed to popen+- Don't define version, release and prefix.+- autoconf vars for name and version+- Copyright -> License+- Use rpm macros for name everywhere+- Use configure and makeinstall macros+- For files use _prefix and only like libdir+- no, the version numbering is not in binary, honest!++* Thu Oct 18 2001 Jens Petersen <juhp@01.246.ne.jp> 0.00.1-1+- added defattr++* Thu Oct 4 2001 Jens Petersen <juhp@01.246.ne.jp> 0.00-1+- first release++%prep++%setup++%build+%configure+make++%install+rm -rf $RPM_BUILD_ROOT++%makeinstall++%clean+rm -rf $RPM_BUILD_ROOT++%files+%defattr(-,root,root)+%doc ChangeLog INSTALL TODO README NEWS AUTHORS COPYING index.html+%{_prefix}/bin/%{name}-config+%{_prefix}/lib/%{name}-%{version}