Permalink
Browse files

Initial import (version 0.63)

  • Loading branch information...
1 parent fd76fb7 commit 52b5516c3a309c144f8e248f2cac709ff1dd63ef Arnaud Quette committed Jun 1, 2012
View
@@ -0,0 +1,3 @@
+Arnaud Quette <aquette.dev@gmail.com>
+Sponsored by MGE UPS SYSTEMS <http://opensource.mgeups.com/>
+
View
@@ -0,0 +1,6 @@
+- segfault on FreeBSD (using -w option).
+- problems with windowed mode (segfault too, or misdrawing).
+
+Please send bug reports to arnaud.quette@free.fr and
+describe the problem as detailed as you can.
+
View
Oops, something went wrong.
View
@@ -0,0 +1,178 @@
+2012-05-10 Arnaud Quette <ArnaudQuette@eaton.com>
+ * wmnut-0.63:
+
+ + acinclude.m4: removed since it's not useful
+ + configure.ac: rework libupsclient detection, using pkg-config, and
+ remove the call to jm_CHECK_TYPE_STRUCT_UTIMBUF (from acinclude.m4).
+ WMNut now requires NUT 2.2.1 minimum!
+ + README: update requirements to NUT 2.2.1 minimum
+ + src/wmnut.{c,h}: switch to UPSCONN_t, as required by recent NUT
+ + config.{sub,guess}, ...: refreshed with the latest autotools
+ + rcfiles.c: fix some warning
+
+2006-01-13 Arnaud Quette <arnaud.quette@mgeups.com>
+ * wmnut-0.62:
+
+ + Disable the XBell detection ad calls as these are not much usefull,
+ and cause some problems with the switch to Xorg and X11R7
+ + Update the missing file
+
+2005-01-05 Arnaud Quette <arnaud.quette@mgeups.com>
+
+ * wmnut-0.61:
+
+ + Switch to NUT 2.0 API (compatible with NUT 1.4 and 2.0)
+ + Rework host handling (autodetection of UPS(s) on host,
+ as you can't anymore address directly an host, ie localhost,
+ without specifying the UPS)
+ + update Mandrake spec file from the official one
+ + Enhanced Solaris support, through getopt modification (thanks to David Butts)
+
+2003-11-08 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.60:
+
+ + Enable libupsclient autodetection (from nut-1.4.1-pre3)
+
+2003-10-18 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.59:
+
+ + better handling of communication with upsd
+ + reworked autoconf mechanism (for autoconf 2.50 or later)
+ by renaming configure.in to configure.ac, and updating
+ various things in configure.ac
+ + reworked Mandrake packaging spec file
+ + xpm icons converted to png for Mandrake packaging.
+
+2003-07-14 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.58:
+
+ + switch command line parsing to getopt() to make it cleaner.
+
+2003-05-internal Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.57:
+
+ + Bug hunting (thanks to P. Marzouk): fixed a bug which prevented from
+ restoring values when a UPS was temporarily unavailable.
+
+2003-04-internal Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.56:
+
+ + Fixed cleaner a minor warning in rcfiles.c (Bill Richter)
+
+2003-03-22 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.55:
+
+ + Dropped out INFO_RUNTIME support to INFO_BATT_RUNTIME only
+ + Re-enabled debug output (through -V option)
+ + Re-enabled blinking communication status on lost communication
+ + Re-enabled code that handle unsupported variables
+ + Enhanced (again) nut files detection and handling in configure.in
+ Now WMNut can detect if the path given for --with-nut-* is a binary
+ installation from source or package, or if it is a source directory.
+ + Back the standard naming scheme, using the pre-defined PACKAGE
+ variable in config.h
+ + Added in contrib a basic ebuild script for Gentoo GNU/Linux
+
+2003-03-20 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.54:
+
+ + Fixed a minor warning in rcfiles.c
+ Thanks to Bill Richter for his help in beta testing:
+ + Fixed a packaging problem (call to autoheader)
+ + Enhanced nut files detection and handling in configure.in
+
+2003-03-09 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.53:
+
+ + Added configure option (--with-nut) to specify a global location
+ (directories) for upsclient.oh.
+
+2003-03-06 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.52:
+
+ + Bug hunting (thanks to Russell Kroll): ignore SIGPIPE, so upsd stop
+ doesn't result in a crash of WMNut (which results in a Wharf crash)
+ + typo fix in Changelog and README (thanks to Bill Richter)
+ + Spell checking and various update (thanks to Bill Richter)
+ + Include autoconf/automake depends (install-sh, config.sub/guess,
+ missing and mkinstalldirs)
+ + Added configure options (--with-nut-libs and --with-nut-includes)
+ to specify location (directories) for upsclient.oh and improved
+ configure rules to automatically check for upsclient.oh
+
+2003-02-16 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.51:
+
+ + (0.30) Switched to new NUT client library (files upsclient.h/o)
+ + (0.40) Switched to autoconf/automake to enhance multi platforms support
+ + Include packaging files for RPM (Mandrake) based
+ + Did a bit of code cleaning.
+ + Fixed some minor bugs
+ + Various minor changes (reformated/renamed CHANGES, ...)
+
+2002-05-05 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.1.0:
+
+ + WMNut now supports multiple host monitoring.
+ + Modified code to hide all values on lost communication.
+ + Enhanced rcfile code.
+ + Enhanced data (NUT) fetch code and add TCP mode.
+ + Enhanced code to handle unsupported values and their display.
+
+2002-03-16 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.0.9:
+
+ + Added rc files support (/etc/wmnutrc and ~/.wmnutrc).
+ + Modified Makefile to allow easy override of various parameters (NUT,
+ X11, install directories).
+ + Replaced "-display" command line option with "-d" (easier, but
+ "-display" is still supported for compatibility).
+ + Modified wmgeneral.h to define WMNUT_NAME (default is wmnut).
+ + Modified code not to bail out every times when accessing unsupported variables.
+ + Reformated help (-h argument) output so it now fits in 80 characters.
+ + Modified code to handle FreeBSD X11 problems (Segfault on XCloseDisplay).
+ + Modified code to handle blinking red "C" when communication is lost.
+ + Fixed Makefile to use CFLAGS instead of COPTS and to include DEBUG flags.
+ + Added full window name (form: "wmnut:upsname", eg "wmnut:el800@localhost").
+ + Did a bit of code cleaning.
+ + Fixed a bug for multiple blinking events at the same time.
+
+2002-01-19 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.0.8:
+
+ + Added blinking battery (Red/Yellow/Green) when On Battery (respectively
+ Critical/Low/High).
+ + Added blinking 'C' when Communication Lost (Data stale).
+ + Modified INSTALL to include "make install-misc" from NUT needed.
+ + Modified fetch code to handle unsupported features (RUNTIME)
+ and other error codes.
+ + Added X11 Atom management to allow clean window close (corrects the
+ "Broken pipe" message when exiting).
+ + Added cleanup on exit (need to be completed).
+ + Added a -w windowed mode (opposite to native withdrawn mode for Window
+ Maker). This allows better window handling on other Window Managers).
+ + Fixed some problems with FreeBSD (forgotten #ifdef).
+ + Did a bit of code cleaning (not completed).
+ + Modified wmnut_master_LowColor.xpm according to wmnut_master.xpm
+ The -l (LowColor) option now works.
+ + Modified wmnut_master*.xpm to make green plug as default (was blue)
+ according to Bill Richter (huge thanks to him for his help !).
+ + Added "-v" option to print WMNUT version and information.
+ + Added "-V" option to print available features and base values.
+
+2002-01-01 Arnaud Quette <arnaud.quette@free.fr>
+
+ * wmnut-0.0.7: initial version.
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.
View
@@ -0,0 +1,4 @@
+
+EXTRA_DIST = BUGS wmnutrc
+
+SUBDIRS = src icons contrib doc
View
@@ -0,0 +1 @@
+See Changelog
Oops, something went wrong.

0 comments on commit 52b5516

Please sign in to comment.