summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard Hughes <richard@hughsie.com>2006-06-05 21:47:28 +0000
committerRichard Hughes <richard@hughsie.com>2006-06-05 21:47:28 +0000
commitbe6bc9d7464bb9897acec10fdf7580aa3d212326 (patch)
tree0c5ef4458956ffafd07df344c52fcb45907ac106
parent7306ce4d2ae22de302034f2d6c69aaf1b8cea9cd (diff)
2006-06-05 Richard Hughes <richard@hughsie.com>
* INSTALL: Add this GNU required file. * man/on_ac_power.1: * man/pm-pmu.1: Newest files (from the SGML files) * .cvsignore: * man/.cvsignore: * pm/.cvsignore: * pm/Makefile.am: * pm/hooks/.cvsignore: * pm/power.d/.cvsignore: * src/.cvsignore: Add these files to keep cvs happy.
-rw-r--r--.cvsignore26
-rw-r--r--ChangeLog18
-rw-r--r--INSTALL236
-rw-r--r--man/.cvsignore3
-rw-r--r--man/on_ac_power.164
-rw-r--r--man/pm-pmu.167
-rw-r--r--pm/.cvsignore2
-rw-r--r--pm/Makefile.am2
-rw-r--r--pm/hooks/.cvsignore2
-rw-r--r--pm/power.d/.cvsignore2
-rw-r--r--src/.cvsignore4
11 files changed, 365 insertions, 61 deletions
diff --git a/.cvsignore b/.cvsignore
index 26481d5..3ee7db6 100644
--- a/.cvsignore
+++ b/.cvsignore
@@ -1 +1,25 @@
-pm-pmu
+aclocal.m4
+autom4te.cache
+config.*
+configure
+depcomp
+install-sh
+intltool-extract
+intltool-merge
+intltool-update
+libtool
+ltmain.sh
+Makefile
+Makefile.in
+*.make
+missing
+stamp-h*
+*.tar.gz
+intltool-extract
+intltool-extract.in
+intltool-merge
+intltool-merge.in
+intltool-update
+intltool-update.in
+mkinstalldirs
+po
diff --git a/ChangeLog b/ChangeLog
index 2fc0041..2052b5e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,23 @@
2006-06-05 Richard Hughes <richard@hughsie.com>
+ * INSTALL:
+ Add this GNU required file.
+
+ * man/on_ac_power.1:
+ * man/pm-pmu.1:
+ Newest files (from the SGML files)
+
+ * .cvsignore:
+ * man/.cvsignore:
+ * pm/.cvsignore:
+ * pm/Makefile.am:
+ * pm/hooks/.cvsignore:
+ * pm/power.d/.cvsignore:
+ * src/.cvsignore:
+ Add these files to keep cvs happy.
+
+2006-06-05 Richard Hughes <richard@hughsie.com>
+
* Makefile:
Remove old build system, as Makefile is now autogenerated.
diff --git a/INSTALL b/INSTALL
new file mode 100644
index 0000000..23e5f25
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1,236 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
+
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+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, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+ 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 you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' 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. Run `./configure --help' for
+details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+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 support 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' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' 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' cannot figure out automatically,
+but needs to determine by the type of machine the package will run on.
+Usually, assuming the package is built to be run on the _same_
+architectures, `configure' can figure that out, but if it prints a
+message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ 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 machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+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.
+
+Defining Variables
+==================
+
+Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script). Here is a another example:
+
+ /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
+configuration-related scripts to be executed by `/bin/bash'.
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--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.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
diff --git a/man/.cvsignore b/man/.cvsignore
new file mode 100644
index 0000000..9f826e0
--- /dev/null
+++ b/man/.cvsignore
@@ -0,0 +1,3 @@
+Makefile
+Makefile.in
+manpage.*
diff --git a/man/on_ac_power.1 b/man/on_ac_power.1
index 4d29c1e..0e2a375 100644
--- a/man/on_ac_power.1
+++ b/man/on_ac_power.1
@@ -1,36 +1,40 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" First parameter, NAME, should be all caps
-.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
-.\" other parameters are allowed: see man(7), man(1)
-.TH ON_AC_POWER 1 "April 2005" "" ""
-.\" Please adjust this date whenever revising the manpage.
-.\"
-.\" Some roff macros, for reference:
-.\" .nh disable hyphenation
-.\" .hy enable hyphenation
-.\" .ad l left justify
-.\" .ad b justify to both left and right margins
-.\" .nf disable filling
-.\" .fi enable filling
-.\" .br insert line break
-.\" .sp <n> insert n+1 empty lines
-.\" for manpage-specific macros, see man(7)
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve ChDone.
+teve@ggi-project.org>.
+.TH "ON_AC_POWER" "1" "05 June 2006" "" ""
+
.SH NAME
on_ac_power \- test whether the computer is running on line power
.SH SYNOPSIS
-.B on_ac_power
-.SH DESCRIPTION
+
+\fBon_ac_power\fR
+
+.SH "DESCRIPTION"
+.PP
+This manual page documents briefly the
+\fBon_ac_power\fR command.
+.PP
+\fBon_ac_power\fR is a command line program to test whether the computer is running on line power
+.SH "EXIT CODES"
+.PP
The command succeeds (status 0) if the system is using line power
and fails (status other than 0) otherwise.
It is designed to be easy to use in shell scripts.
-.SH OPTIONS
-None.
-.SH "EXIT STATUS"
-.br
-.nf
-\fB0\fR (true) System is on line power
-\fB1\fR (false) System is not on line power
-\fB255\fR (false) Power status could not be determined
-.SH NOTES
-Absence of any batteries is taken to mean that the system is on line power.
-
+.TP
+\fB 0 (true) \fR
+System is on line power.
+.TP
+\fB 1 (false) \fR
+System is not on line power.
+.TP
+\fB 255 (false) \fR
+Power status could not be determined.
+.SH "SEE ALSO"
+.PP
+pm-suspend (1).
+.SH "AUTHOR"
+.PP
+This manual page was written by Richard Hughes <richard@hughsie.com>\&.
diff --git a/man/pm-pmu.1 b/man/pm-pmu.1
index 349fdb4..a51ab68 100644
--- a/man/pm-pmu.1
+++ b/man/pm-pmu.1
@@ -1,40 +1,49 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" First parameter, NAME, should be all caps
-.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
-.\" other parameters are allowed: see man(7), man(1)
-.TH PM-PMU 1 "May 2006" "" ""
-.\" Please adjust this date whenever revising the manpage.
-.\"
-.\" Some roff macros, for reference:
-.\" .nh disable hyphenation
-.\" .hy enable hyphenation
-.\" .ad l left justify
-.\" .ad b justify to both left and right margins
-.\" .nf disable filling
-.\" .fi enable filling
-.\" .br insert line break
-.\" .sp <n> insert n+1 empty lines
-.\" for manpage-specific macros, see man(7)
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to SteDone.
+ng <steve@ggi-project.org>.
+.TH "PM-PMU" "1" "05 June 2006" "" ""
+
.SH NAME
pm-pmu \- suspend the computer on machines using a Macintosh-style PMU
.SH SYNOPSIS
-.B pm-pmu --suspend
-.SH DESCRIPTION
+
+\fBpm-pmu\fR
+
+.SH "DESCRIPTION"
+.PP
+This manual page documents briefly the
+\fBpm-pmu\fR command.
+.PP
+\fBpm-pmu\fR is a command line program to test whether the computer is running on line power
+.SH "EXIT CODES"
+.PP
The command succeeds (status 0) if the machine uses a Macintosh-style
PMU, and suspended successfully. The command fails (status other than
0) otherwise.
It is designed to be easy to use in shell scripts.
-.SH OPTIONS
.TP
-.BI "--suspend"
+\fB 0 (true) \fR
+System was suspended using PMU.
+.TP
+\fB 1 (false) \fR
+System could not be suspended using PMU.
+.SH "OPTIONS"
+.PP
+This program follows the usual GNU command line syntax,
+with long options starting with two dashes (`-'). A summary of
+options is included below.
+.TP
+\fB --suspend \fR
Suspend the computer.
-.br
.TP
-.BI "--help"
+\fB --help \fR
Show help message.
-.br
-.SH "EXIT STATUS"
-.br
-.nf
-\fB0\fR (true) System was suspended using PMU
-\fB1\fR (false) System could not be suspended using PMU
+.SH "SEE ALSO"
+.PP
+pm-suspend (1).
+.SH "AUTHOR"
+.PP
+This manual page was written by Richard Hughes <richard@hughsie.com>\&.
diff --git a/pm/.cvsignore b/pm/.cvsignore
new file mode 100644
index 0000000..282522d
--- /dev/null
+++ b/pm/.cvsignore
@@ -0,0 +1,2 @@
+Makefile
+Makefile.in
diff --git a/pm/Makefile.am b/pm/Makefile.am
index ad59107..fe3c413 100644
--- a/pm/Makefile.am
+++ b/pm/Makefile.am
@@ -1,4 +1,4 @@
-SUBDIRS = hooks power.d
+SUBDIRS = hooks power.d config.d
extradir = $(sysconfdir)/pm
diff --git a/pm/hooks/.cvsignore b/pm/hooks/.cvsignore
new file mode 100644
index 0000000..282522d
--- /dev/null
+++ b/pm/hooks/.cvsignore
@@ -0,0 +1,2 @@
+Makefile
+Makefile.in
diff --git a/pm/power.d/.cvsignore b/pm/power.d/.cvsignore
new file mode 100644
index 0000000..282522d
--- /dev/null
+++ b/pm/power.d/.cvsignore
@@ -0,0 +1,2 @@
+Makefile
+Makefile.in
diff --git a/src/.cvsignore b/src/.cvsignore
new file mode 100644
index 0000000..684b014
--- /dev/null
+++ b/src/.cvsignore
@@ -0,0 +1,4 @@
+.deps
+Makefile
+Makefile.in
+pm-pmu