summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst86
1 files changed, 68 insertions, 18 deletions
diff --git a/README.rst b/README.rst
index cdee008..8aeeb48 100644
--- a/README.rst
+++ b/README.rst
@@ -7,14 +7,22 @@
:target: https://scan.coverity.com/projects/jamesodhunt-procenv
:alt: Coverity Scan Build Status
-.. image:: https://img.shields.io/badge/donate-flattr-red.svg
+.. image:: https://img.shields.io/badge/donate-flattr-blue.svg
:alt: Donate via flattr
:target: https://flattr.com/profile/jamesodhunt
+.. image:: https://img.shields.io/badge/paypal-donate-blue.svg
+ :alt: Donate via Paypal
+ :target: https://www.paypal.me/jamesodhunt
+
=======
procenv
=======
+.. raw:: html
+
+ <a href="https://asciinema.org/a/118278"><img src="https://asciinema.org/a/118278.png" width="836"/></a>
+
.. contents::
.. sectnum::
@@ -28,15 +36,25 @@ it runs, in well-structured plain ASCII, JSON (YAML), XML or CSV.
It is useful as a test tool, to understand what environment a process
runs in and for system comparison.
-``procenv`` runs on Linux, FreeBSD, kFreeBSD, GNU Hurd and Android. It
-unashamedly emulates a number of existing system utilities as it is
-attempting to be all-encompassing: I wrote it with the aim of being able
-to dump "everything" that a process may care about by simply running a
-single program (by default). Also, the line of demarcation between
-"process", "program" and "system" is slightly blurry in some aspects.
-For example ``sysconf(3)`` variables could arguably be considered system
-attributes, but procenv shows these too since they are obviously meant
-to be queryable by applications.
+``procenv`` runs on the following operating systems:
+
+- Android
+- FreeBSD
+- GNU Hurd
+- GNU Linux
+- Minix 3
+- NetBSD
+- OpenBSD
+- OSX
+
+It unashamedly emulates a number of existing system
+utilities as it is attempting to be all-encompassing: I wrote it with
+the aim of being able to dump "everything" that a process may care about
+by simply running a single program (by default). Also, the line of
+demarcation between "process", "program" and "system" is slightly
+blurry in some aspects. For example ``sysconf(3)`` variables could
+arguably be considered system attributes, but procenv shows these too
+since they are obviously meant to be queryable by applications.
.. [#] If you find anything missing, please either raise a bug or send a
patch :)
@@ -51,6 +69,12 @@ build including running itself so that the build environment gets
captured in the builds logs themselves. Select a link below and drill
down to the build log to see the ``procenv`` output:
+Semaphore-CI
+~~~~~~~~~~~~
+
+* https://semaphoreci.com/jamesodhunt/procenv
+ (Click "Passed", "Job #", then "``make check``" to see output).
+
Travis-CI
~~~~~~~~~
@@ -90,24 +114,39 @@ https://code.launchpad.net/~jamesodhunt/+recipe/procenv-daily
Ubuntu Autopkgtest (DEP-8) environment
......................................
-* https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-procenv/
-* https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-procenv/
-* https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-procenv/
-* https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-procenv/
+* http://autopkgtest.ubuntu.com/packages/p/procenv/
+
+* Old Jenkins system
+
+ * https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-procenv/
+
+ * https://jenkins.qa.ubuntu.com/view/Vivid/view/AutoPkgTest/job/vivid-adt-procenv/
+
+ * https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-procenv/
+
+ * https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-procenv/
The ``sbuild`` tool environment
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+...............................
``procenv`` gets run from within sbuild via a DEP-8 test:
-* https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-sbuild/
+* http://autopkgtest.ubuntu.com/packages/s/sbuild/
+
+* Old Jenkins system
+
+ * https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-sbuild/
The ``pbuilder`` tool environment
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.................................
``procenv`` gets run from within pbuilder via a DEP-8 test:
-* https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-pbuilder/
+* http://autopkgtest.ubuntu.com/packages/p/pbuilder/
+
+* Old Jenkins system
+
+ * https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-pbuilder/
Debian
~~~~~~
@@ -122,12 +161,23 @@ Debian autopkgtest (DEP-8) environment
* http://ci.debian.net/#package/procenv
+Fedora
+~~~~~~
+
+* https://admin.fedoraproject.org/pkgdb/package/rpms/procenv/
+ (click "Builds status", click a build, then click one of the "build logs" links).
+
FreeBSD
~~~~~~~
Logs used to be available, but sadly it appears pointyhat.freebsd.com has
been taken offline (any replacement?)
+Gentoo
+~~~~~~
+
+* https://packages.gentoo.org/packages/sys-process/procenv/
+
Porting
-------