Library for dealing with system processes
91
stars
900
commits
Haskell
primary language
Jun 11, 2026
updated
process Package See process on Hackage for
more information.
To build this package using Cabal directly from Git, you must run
autoreconf -i before the usual Cabal build steps (cabal {configure,build,install}). The program autoreconf is part of
GNU autoconf. There is no
need to run the configure script: cabal configure will do this for
you.
Some generated files not tracked in the git repository are included in
a source (sdist) distribution, including
include/HsProcessConfig.h.in and configure. Maintainers who are
producing a release of process, for example to upload to Hackage,
should ensure that they run the following to generate fresh files:
git clean -fxd
autoconf -i
(WARNING: git clean -fxd will delete all untracked files in the
repo)
To make the release process more observable and less dependent on the system of the maintainer, there's a workflow creating an sdist.
This sdist ought to be generated as follows:
workflow_dispatch event trigger" that you will find there.posix_spawn_file_actions_addchdir_np is presentsdist. Upload it as a candidate and proceed as usual.Haskell
64.6%
C
25.8%
JavaScript
8.5%
Library for dealing with system processes
91
stars
900
commits
Haskell
primary language
Jun 11, 2026
updated
process Package See process on Hackage for
more information.
To build this package using Cabal directly from Git, you must run
autoreconf -i before the usual Cabal build steps (cabal {configure,build,install}). The program autoreconf is part of
GNU autoconf. There is no
need to run the configure script: cabal configure will do this for
you.
Some generated files not tracked in the git repository are included in
a source (sdist) distribution, including
include/HsProcessConfig.h.in and configure. Maintainers who are
producing a release of process, for example to upload to Hackage,
should ensure that they run the following to generate fresh files:
git clean -fxd
autoconf -i
(WARNING: git clean -fxd will delete all untracked files in the
repo)
To make the release process more observable and less dependent on the system of the maintainer, there's a workflow creating an sdist.
This sdist ought to be generated as follows:
workflow_dispatch event trigger" that you will find there.posix_spawn_file_actions_addchdir_np is presentsdist. Upload it as a candidate and proceed as usual.Haskell
64.6%
C
25.8%
JavaScript
8.5%