uacpid: Userspace Advanced Configuration and Power Interface event daemon

[ bsd3, program, system ] [ Propose Tags ]

uacpid is a daemon designed to be run in userspace that will monitor the local system's acpid socket for hardware events. These events can then be acted upon by handlers with access to the user's environment.

[Skip to Readme]

Downloads

uacpid-1.0.3.0.tar.gz [browse] (Cabal source package)
Package description (revised from the package)

Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

DinoMorelli

For package maintainers and hackage trustees

edit package information

Candidates

No Candidates

Versions [RSS]	0.0.2, 0.0.3, 0.0.4, 1.0.1, 1.0.3.0, 1.1, 1.2
Dependencies	base (>=3 && <5), containers, directory, filepath, hslogger, mtl, network, old-locale, process, regex-compat, time (<1.5), unix [details]
License	BSD-3-Clause
Copyright	2009, 2010 Dino Morelli
Author	Dino Morelli
Maintainer	Dino Morelli <dino@ui3.info>
Revised	Revision 1 made by AdamBergmark at 2015-06-30T01:55:48Z
Category	System
Home page	http://ui3.info/d/proj/uacpid.html
Uploaded	by DinoMorelli at 2011-03-18T19:19:46Z
Distributions
Reverse Dependencies	1 direct, 0 indirect [details]
Executables	uacpid
Downloads	6465 total (25 in the last 30 days)
Rating	(no votes yet) [estimated by Bayesian average]
Your Rating	λ λ λ
Status	Docs not available [build log] Last success reported on 2015-05-21 [all 7 reports]

Readme for uacpid-1.0.3.0

[back to package description]

-----
Getting started developing:

This daemon is designed to make files for itself in ~/.uacpid/ the
first time it's run. To assist with development, there is a script
which will build a development installation and execution environment
in /tmp/uacpid-dev/ for you.


To initialize for development:

   $ bin/uacpid-dev-setup


Once that's completed, it can be run like this:

   $ bin/uacpid-dev


-----
A word about the version numbering scheme:

   4-part: major.minor.status.build
   3-part: major.status.build

   status:
      0 alpha
      1 beta
      2 release candidate
      3 release

   examples:
      1.3.0.2         v1.3 alpha build 2
      1.2.1.0         v1.2 beta build 0
      4.2.24          v4 release candidate build 24
      2.10.3.5        v2.10 release build 5 (say they were bug fixes)
      1.5.2.20090818  Can even use a date for build
                      v1.5 release candidate 2009-08-18 build