Hello community,
here is the log from the commit of package powersave
checked in at Tue Nov 20 14:59:51 CET 2007.
--------
--- powersave/powersave.changes 2007-10-21 22:06:16.000000000 +0200
+++ /mounts/work_src_done/STABLE/powersave/powersave.changes 2007-11-20 12:34:21.000000000 +0100
@@ -1,0 +2,7 @@
+Tue Nov 20 12:33:47 CET 2007 - hmacht@suse.de
+
+- update acpi_hotkeys_ASUS_M6842NW script
+- fix some compiler warnings
+- r3118
+
+-------------------------------------------------------------------
Old:
----
powersave-0.15.18.tar.bz2
New:
----
powersave-0.15.19.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ powersave.spec ++++++
--- /var/tmp/diff_new_pack.tL8871/_old 2007-11-20 14:59:43.000000000 +0100
+++ /var/tmp/diff_new_pack.tL8871/_new 2007-11-20 14:59:43.000000000 +0100
@@ -1,5 +1,5 @@
#
-# spec file for package powersave (Version 0.15.18)
+# spec file for package powersave (Version 0.15.19)
#
# Copyright (c) 2007 SUSE LINUX Products GmbH, Nuernberg, Germany.
# This file and all modifications and additions to the pristine
@@ -11,10 +11,10 @@
# norootforbuild
Name: powersave
-BuildRequires: dbus-1-glib-devel gcc-c++ liblazy lynx pkgconfig
+BuildRequires: dbus-1-glib-devel gcc-c++ liblazy-devel lynx pkgconfig
Url: http://powersave.sourceforge.net/
Summary: General Powermanagement daemon supporting APM and ACPI and CPU frequency scaling
-Version: 0.15.18
+Version: 0.15.19
Release: 1
License: GPL v2 only; GPL v2 or later
Group: System/Daemons
@@ -164,6 +164,10 @@
%defattr(-,root,root)
%_libdir/lib*.so*
%changelog
+* Tue Nov 20 2007 - hmacht@suse.de
+- update acpi_hotkeys_ASUS_M6842NW script
+- fix some compiler warnings
+- r3118
* Sun Oct 21 2007 - hmacht@suse.de
- revert some of the last changes and leave some of the gcc 4.3
warnings for now
++++++ powersave-0.15.18.tar.bz2 -> powersave-0.15.19.tar.bz2 ++++++
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/compile new/powersave-0.15.19/compile
--- old/powersave-0.15.18/compile 2007-10-21 21:24:46.000000000 +0200
+++ new/powersave-0.15.19/compile 1970-01-01 01:00:00.000000000 +0100
@@ -1,142 +0,0 @@
-#! /bin/sh
-# Wrapper for compilers which do not understand `-c -o'.
-
-scriptversion=2005-05-14.22
-
-# Copyright (C) 1999, 2000, 2003, 2004, 2005 Free Software Foundation, Inc.
-# Written by Tom Tromey .
-#
-# This program is free software; you can redistribute it and/or modify
-# it under the terms of the GNU General Public License as published by
-# the Free Software Foundation; either version 2, or (at your option)
-# any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
-
-# As a special exception to the GNU General Public License, if you
-# distribute this file as part of a program that contains a
-# configuration script generated by Autoconf, you may include it under
-# the same distribution terms that you use for the rest of that program.
-
-# This file is maintained in Automake, please report
-# bugs to or send patches to
-# .
-
-case $1 in
- '')
- echo "$0: No command. Try \`$0 --help' for more information." 1>&2
- exit 1;
- ;;
- -h | --h*)
- cat <<\EOF
-Usage: compile [--help] [--version] PROGRAM [ARGS]
-
-Wrapper for compilers which do not understand `-c -o'.
-Remove `-o dest.o' from ARGS, run PROGRAM with the remaining
-arguments, and rename the output as expected.
-
-If you are trying to build a whole package this is not the
-right script to run: please start by reading the file `INSTALL'.
-
-Report bugs to .
-EOF
- exit $?
- ;;
- -v | --v*)
- echo "compile $scriptversion"
- exit $?
- ;;
-esac
-
-ofile=
-cfile=
-eat=
-
-for arg
-do
- if test -n "$eat"; then
- eat=
- else
- case $1 in
- -o)
- # configure might choose to run compile as `compile cc -o foo foo.c'.
- # So we strip `-o arg' only if arg is an object.
- eat=1
- case $2 in
- *.o | *.obj)
- ofile=$2
- ;;
- *)
- set x "$@" -o "$2"
- shift
- ;;
- esac
- ;;
- *.c)
- cfile=$1
- set x "$@" "$1"
- shift
- ;;
- *)
- set x "$@" "$1"
- shift
- ;;
- esac
- fi
- shift
-done
-
-if test -z "$ofile" || test -z "$cfile"; then
- # If no `-o' option was seen then we might have been invoked from a
- # pattern rule where we don't need one. That is ok -- this is a
- # normal compilation that the losing compiler can handle. If no
- # `.c' file was seen then we are probably linking. That is also
- # ok.
- exec "$@"
-fi
-
-# Name of file we expect compiler to create.
-cofile=`echo "$cfile" | sed -e 's|^.*/||' -e 's/\.c$/.o/'`
-
-# Create the lock directory.
-# Note: use `[/.-]' here to ensure that we don't use the same name
-# that we are using for the .o file. Also, base the name on the expected
-# object file name, since that is what matters with a parallel build.
-lockdir=`echo "$cofile" | sed -e 's|[/.-]|_|g'`.d
-while true; do
- if mkdir "$lockdir" >/dev/null 2>&1; then
- break
- fi
- sleep 1
-done
-# FIXME: race condition here if user kills between mkdir and trap.
-trap "rmdir '$lockdir'; exit 1" 1 2 15
-
-# Run the compile.
-"$@"
-ret=$?
-
-if test -f "$cofile"; then
- mv "$cofile" "$ofile"
-elif test -f "${cofile}bj"; then
- mv "${cofile}bj" "$ofile"
-fi
-
-rmdir "$lockdir"
-exit $ret
-
-# Local Variables:
-# mode: shell-script
-# sh-indentation: 2
-# eval: (add-hook 'write-file-hooks 'time-stamp)
-# time-stamp-start: "scriptversion="
-# time-stamp-format: "%:y-%02m-%02d.%02H"
-# time-stamp-end: "$"
-# End:
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/configure new/powersave-0.15.19/configure
--- old/powersave-0.15.18/configure 2007-10-21 22:03:24.000000000 +0200
+++ new/powersave-0.15.19/configure 2007-11-20 12:31:04.000000000 +0100
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.61 for powersave 0.15.18.
+# Generated by GNU Autoconf 2.61 for powersave 0.15.19.
#
# Report bugs to .
#
@@ -728,8 +728,8 @@
# Identity of this package.
PACKAGE_NAME='powersave'
PACKAGE_TARNAME='powersave'
-PACKAGE_VERSION='0.15.18'
-PACKAGE_STRING='powersave 0.15.18'
+PACKAGE_VERSION='0.15.19'
+PACKAGE_STRING='powersave 0.15.19'
PACKAGE_BUGREPORT='hmacht@suse.de'
ac_unique_file="daemon/powersaved.cpp"
@@ -1420,7 +1420,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures powersave 0.15.18 to adapt to many kinds of systems.
+\`configure' configures powersave 0.15.19 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1490,7 +1490,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of powersave 0.15.18:";;
+ short | recursive ) echo "Configuration of powersave 0.15.19:";;
esac
cat <<\_ACEOF
@@ -1613,7 +1613,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-powersave configure 0.15.18
+powersave configure 0.15.19
generated by GNU Autoconf 2.61
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
@@ -1627,7 +1627,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by powersave $as_me 0.15.18, which was
+It was created by powersave $as_me 0.15.19, which was
generated by GNU Autoconf 2.61. Invocation command line was
$ $0 $@
@@ -2317,7 +2317,7 @@
# Define the identity of the package.
PACKAGE='powersave'
- VERSION='0.15.18'
+ VERSION='0.15.19'
cat >>confdefs.h <<_ACEOF
@@ -24048,7 +24048,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by powersave $as_me 0.15.18, which was
+This file was extended by powersave $as_me 0.15.19, which was
generated by GNU Autoconf 2.61. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -24101,7 +24101,7 @@
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF
ac_cs_version="\\
-powersave config.status 0.15.18
+powersave config.status 0.15.19
configured by $0, generated by GNU Autoconf 2.61,
with options \\"`echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\"
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/configure.ac new/powersave-0.15.19/configure.ac
--- old/powersave-0.15.18/configure.ac 2007-10-21 21:24:40.000000000 +0200
+++ new/powersave-0.15.19/configure.ac 2007-11-20 12:30:51.000000000 +0100
@@ -3,7 +3,7 @@
AC_PREREQ(2.59)
-AC_INIT(powersave, 0.15.18, hmacht@suse.de)
+AC_INIT(powersave, 0.15.19, hmacht@suse.de)
AM_INIT_AUTOMAKE
AC_CONFIG_SRCDIR([daemon/powersaved.cpp])
AM_CONFIG_HEADER(config.h)
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/contrib/acpi_hotkeys_ASUS_M6842NW new/powersave-0.15.19/contrib/acpi_hotkeys_ASUS_M6842NW
--- old/powersave-0.15.18/contrib/acpi_hotkeys_ASUS_M6842NW 2007-10-21 21:24:09.000000000 +0200
+++ new/powersave-0.15.19/contrib/acpi_hotkeys_ASUS_M6842NW 2007-11-20 12:30:50.000000000 +0100
@@ -80,7 +80,7 @@
run_on_xserver "/opt/kde3/bin/dcop kaffeine KaffeineIface stop" &
: # kaffeine is running, press stop
else
- eject /dev/hdc
+ eject /dev/dvd
: # kaffeine is not running, eject CD/DVD
fi
: # stop
@@ -89,7 +89,7 @@
run_on_xserver "/opt/kde3/bin/dcop kaffeine KaffeineIface pause" &
: # play button in kaffeine
else
- media=`cd-info --no-tracks --no-cddb --no-device-info --dvd --no-header --cdrom-device=/dev/hdc 2>/dev/null | grep "Disc mode is listed as:" | awk -F ": " '{print $2}'`
+ media=`cd-info --no-tracks --no-cddb --no-device-info --dvd --no-header --cdrom-device=/dev/dvd 2>/dev/null | grep 'Disc\ mode\ is\ listed\ as:' | awk -F ": " '{print $2}'`
case "$media" in
CD-DA)
run_on_xserver "/opt/kde3/bin/kaffeine AudioCD >/dev/null 2>&1"
@@ -121,12 +121,12 @@
# disable wlan
echo 1 > "${RF_KILL}"
# switch off wlan LED
- echo 0 > /proc/acpi/asus/wled
+ echo 0 > /sys/devices/platform/asus-laptop/wlan
else
# enable wlan
echo 0 > "${RF_KILL}"
# turn on wlan LED
- echo 1 > /proc/acpi/asus/wled
+ echo 1 > /sys/devices/platform/asus-laptop/wlan
fi
fi
: # togle wlan state activated/deactivated
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/daemon/brightness.cpp new/powersave-0.15.19/daemon/brightness.cpp
--- old/powersave-0.15.18/daemon/brightness.cpp 2007-10-21 21:24:33.000000000 +0200
+++ new/powersave-0.15.19/daemon/brightness.cpp 2007-11-20 12:30:50.000000000 +0100
@@ -142,7 +142,7 @@
if (!_supported)
return -1;
- char *prop = "laptop_panel.num_levels";
+ const char *prop = "laptop_panel.num_levels";
int num_levels;
liblazy_hal_get_property_int((char*)_udi.c_str(), prop, &num_levels);
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/daemon/cpufreq_management.cpp new/powersave-0.15.19/daemon/cpufreq_management.cpp
--- old/powersave-0.15.18/daemon/cpufreq_management.cpp 2007-10-21 21:24:32.000000000 +0200
+++ new/powersave-0.15.19/daemon/cpufreq_management.cpp 2007-11-20 12:30:50.000000000 +0100
@@ -81,7 +81,7 @@
return _is_supported;
}
-bool CpufreqManagement::setGovernor(char *governor)
+bool CpufreqManagement::setGovernor(const char *governor)
{
return DBus_Server::sendMethodCallAndBlock(DBUS_HAL_INTERFACE,
_hal_device.c_str(),
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/daemon/cpufreq_management.h new/powersave-0.15.19/daemon/cpufreq_management.h
--- old/powersave-0.15.18/daemon/cpufreq_management.h 2007-10-21 21:24:30.000000000 +0200
+++ new/powersave-0.15.19/daemon/cpufreq_management.h 2007-11-20 12:30:50.000000000 +0100
@@ -94,7 +94,7 @@
*
* @return true on success, false otherwise
*/
- bool setGovernor(char *governor);
+ bool setGovernor(const char *governor);
/** @brief sets the performance for a dynamic scaling mechanism
*
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/docs/powersave.8 new/powersave-0.15.19/docs/powersave.8
--- old/powersave-0.15.18/docs/powersave.8 2007-10-21 22:05:57.000000000 +0200
+++ new/powersave-0.15.19/docs/powersave.8 2007-11-20 12:31:19.000000000 +0100
@@ -131,7 +131,7 @@
List all power schemes. Also shows which one is the current active one
and which are activated if power source changes to AC or battery power.
Configuration files for schemes are by default
-located in /etc/powersave/scheme_*. A scheme
+located in /usr/local/etc/powersave/scheme_*. A scheme
changes the power save policy of the powersave daemon. Changing the
power source (AC/Battery) normally switches the power policy/scheme. Use -e option
to switch between schemes manually.
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/docs/powersaved.8 new/powersave-0.15.19/docs/powersaved.8
--- old/powersave-0.15.18/docs/powersaved.8 2007-10-21 22:05:57.000000000 +0200
+++ new/powersave-0.15.19/docs/powersaved.8 2007-11-20 12:31:19.000000000 +0100
@@ -29,12 +29,12 @@
.TP
.I -x
Set the path to executables that will be executed depending on the
-events configuration file (default: /usr/lib/powersave/scripts)
+events configuration file (default: /usr/local/libexec/powersave/scripts)
.TP
.I -y
Set the path to executables that will be executed for internal events
-and by the event scripts (default: /usr/lib/powersave)
+and by the event scripts (default: /usr/local/libexec/powersave)
.TP
.I -d
@@ -50,7 +50,7 @@
.TP
.I -c DIR
-Sets the configuration directory (default /etc/powersave).
+Sets the configuration directory (default /usr/local/etc/powersave).
General configuration files are:
battery
common
@@ -63,7 +63,7 @@
.TP
.I -s DIR
Sets the directory for Scheme configuration files (new ones could be
-added and switched to, default is /etc/powersave):
+added and switched to, default is /usr/local/etc/powersave):
scheme_performance (default scheme when working on AC power)
scheme_powersave (default scheme when working on battery power)
@@ -109,7 +109,7 @@
developers who helped to create this software.
.SH SEE ALSO
.B powersave(8)
-.B /etc/powersave/*
-.B /usr/share/doc/powersave
+.B /usr/local/etc/powersave/*
+.B /usr/local/share/doc/powersave
.B http://powersave.sourceforge.net
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/INSTALL new/powersave-0.15.19/INSTALL
--- old/powersave-0.15.18/INSTALL 2007-10-21 22:03:40.000000000 +0200
+++ new/powersave-0.15.19/INSTALL 2007-11-20 12:31:09.000000000 +0100
@@ -1,61 +1,234 @@
- @section Get the Sources
+Installation Instructions
+*************************
- @subsection Get the Tarball
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006 Free Software Foundation, Inc.
- You can download CVS HEAD tarballs via the CVSweb frontend:
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
- powersave: @uref{http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/powersave/powersave/powersave.tar.gz?tarball=1&only_with_tag=HEAD}
+Basic Installation
+==================
+
+Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.
+
+ 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 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.
+
+ Running `configure' might take a while. 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=c99 CFLAGS=-g 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 can use 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 `..'.
+
+ With a non-GNU `make', it is safer 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).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
+
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/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.
- The clients can be found here: @*
- kpowersave: @uref{http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/powersave/kpowersave/kpowersave.tar.gz?tarball=1&only_with_tag=HEAD}
- wmpowersave: @uref{http://forge.novell.com/modules/xfmod/cvs/cvsbrowse.php/powersave/wmpowersave/wmpowersave.tar.gz?tarball=1&only_with_tag=HEAD}
-
- @subsection Get the CVS Sources
-
- export CVS_RSH=ssh
- cvs -z3 -d:ext:anonymous@@forgecvs1.novell.com:/cvsroot/powersave co modulename
-
- The module you wish to check out must be specified as modulename
- (either 'powersave', 'kpowersave' or 'wmpowersave').
- When prompted for the password, simply enter "anonymous".
-
- We'll try to let HEAD stay in good shape all the time but well,
- you never know. Tell us if you find bugs or have problems compiling.
-
- @section Compiling
-
- In the powersave directory do:
- @enumerate
-
- @item
- autoreconf -fi
- ./configure --prefix=/usr
-
- (./configure --help gives further instructions (recommended))
-
- @item
- If no error occures type "make"
-
- @item
- change the user to root (su root) and type "make install"
- @end enumerate
-
- @section Needed Packages for Compiling
-
- This list is probably not complete, but gives an overview:
-
- @itemize
- @item
- libstd-c++
- @item
- g++
- @item
- autoconf
- @item
- automake
- @item
- libtool
- @item
- @dots{}
- @end itemize
-
\ No newline at end of file
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/Makefile.in new/powersave-0.15.19/Makefile.in
--- old/powersave-0.15.18/Makefile.in 2007-10-21 22:03:29.000000000 +0200
+++ new/powersave-0.15.19/Makefile.in 2007-11-20 12:31:09.000000000 +0100
@@ -35,8 +35,8 @@
DIST_COMMON = README $(am__configure_deps) $(srcdir)/Makefile.am \
$(srcdir)/Makefile.in $(srcdir)/config.h.in \
$(top_srcdir)/configure AUTHORS COPYING ChangeLog INSTALL NEWS \
- TODO compile config.guess config.sub depcomp install-sh \
- ltmain.sh missing
+ TODO config.guess config.sub depcomp install-sh ltmain.sh \
+ missing
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/configure.ac
am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
@@ -463,6 +463,10 @@
tardir=$(distdir) && $(am__tar) | bzip2 -9 -c >$(distdir).tar.bz2
$(am__remove_distdir)
+dist-lzma: distdir
+ tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma
+ $(am__remove_distdir)
+
dist-tarZ: distdir
tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z
$(am__remove_distdir)
@@ -489,6 +493,8 @@
GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(am__untar) ;;\
*.tar.bz2*) \
bunzip2 -c $(distdir).tar.bz2 | $(am__untar) ;;\
+ *.tar.lzma*) \
+ unlzma -c $(distdir).tar.lzma | $(am__untar) ;;\
*.tar.Z*) \
uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
*.shar.gz*) \
@@ -640,8 +646,8 @@
.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
all all-am am--refresh check check-am clean clean-generic \
clean-libtool ctags ctags-recursive dist dist-all dist-bzip2 \
- dist-gzip dist-shar dist-tarZ dist-zip distcheck distclean \
- distclean-generic distclean-hdr distclean-libtool \
+ dist-gzip dist-lzma dist-shar dist-tarZ dist-zip distcheck \
+ distclean distclean-generic distclean-hdr distclean-libtool \
distclean-tags distcleancheck distdir distuninstallcheck dvi \
dvi-am html html-am info info-am install install-am \
install-data install-data-am install-dvi install-dvi-am \
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/scripts/rcpowersaved new/powersave-0.15.19/scripts/rcpowersaved
--- old/powersave-0.15.18/scripts/rcpowersaved 2007-10-21 22:05:56.000000000 +0200
+++ new/powersave-0.15.19/scripts/rcpowersaved 2007-11-20 12:31:19.000000000 +0100
@@ -53,8 +53,8 @@
### END INIT INFO
# Check for missing binaries (stale symlinks should not happen)
-powersaved_BIN=/usr/sbin/powersaved
-powersave_BIN=/usr/bin/powersave
+powersaved_BIN=/usr/local/sbin/powersaved
+powersave_BIN=/usr/local/bin/powersave
ACPID_BIN=/sbin/acpid
S2RAM_BIN=/usr/sbin/s2ram
# this is the default set of acpi modules loaded if nothing is configured
@@ -63,7 +63,7 @@
test -x $powersaved_BIN || exit 5
# Check for existence of needed config file and read it
-CONFIG=/etc/powersave
+CONFIG=/usr/local/etc/powersave
# create symlink to /etc where powersave expects configuration files.
# this is an evil hack and is only needed when updating from powersave
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/scripts/setDefaultTrippoints.sh new/powersave-0.15.19/scripts/setDefaultTrippoints.sh
--- old/powersave-0.15.18/scripts/setDefaultTrippoints.sh 2007-10-21 22:05:56.000000000 +0200
+++ new/powersave-0.15.19/scripts/setDefaultTrippoints.sh 2007-11-20 12:31:19.000000000 +0100
@@ -66,13 +66,13 @@
if [ -d /dev/shm ] && [ -w /dev/shm ] && [ -x /dev/shm ];then
THERMAL_TRIPPOINTS_FILE="/dev/shm/thermal_trippoints_file"
- /usr/bin/powersave -T > $THERMAL_TRIPPOINTS_FILE
+ /usr/local/bin/powersave -T > $THERMAL_TRIPPOINTS_FILE
if [ $? != 0 ];then
exit 1
fi
elif [ -d /tmp ] && [ -w /tmp ] && [ -x /tmp ];then
THERMAL_TRIPPOINTS_FILE="/tmp/thermal_trippoints_file"
- /usr/bin/powersave -T > $THERMAL_TRIPPOINTS_FILE
+ /usr/local/bin/powersave -T > $THERMAL_TRIPPOINTS_FILE
if [ $? != 0 ];then
exit 1
fi
@@ -82,7 +82,7 @@
fi
if [ "$CONFIG_FILE" = "" ];then
- for y in /etc/powersave/scheme_*; do
+ for y in /usr/local/etc/powersave/scheme_*; do
if [ ! -w "$y" ];then
echo "Cannot access config file $y"
exit 1
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/powersave-0.15.18/user_binary/powersave.cpp new/powersave-0.15.19/user_binary/powersave.cpp
--- old/powersave-0.15.18/user_binary/powersave.cpp 2007-10-21 21:22:51.000000000 +0200
+++ new/powersave-0.15.19/user_binary/powersave.cpp 2007-11-20 12:30:47.000000000 +0100
@@ -98,7 +98,7 @@
"running and use -v to increase verbose level and have a look into syslog.\n");
}
-void privilege_error(char *privilege)
+void privilege_error(const char *privilege)
{
fprintf(stderr, "User is not allowed for %s according to PolicyKit.\n", privilege);
}
@@ -687,7 +687,7 @@
}
}
if (PERFORMANCE_SPEED) {
- char *governor = "performance";
+ const char *governor = "performance";
if (liblazy_dbus_system_send_method_call(DBUS_HAL_INTERFACE,
HAL_UDI_COMPUTER,
DBUS_HAL_CPUFREQ_INTERFACE,
@@ -701,7 +701,7 @@
} else
printf("Policy set to performance\n");
} else if (POWERSAVE_SPEED) {
- char *governor = "powersave";
+ const char *governor = "powersave";
if (liblazy_dbus_system_send_method_call(DBUS_HAL_INTERFACE,
HAL_UDI_COMPUTER,
DBUS_HAL_CPUFREQ_INTERFACE,
@@ -715,7 +715,7 @@
} else
printf("Policy set to powersave\n");
} else if (DYNAMIC_SPEED) {
- char *governor = "ondemand";
+ const char *governor = "ondemand";
if (liblazy_dbus_system_send_method_call(DBUS_HAL_INTERFACE,
HAL_UDI_COMPUTER,
DBUS_HAL_CPUFREQ_INTERFACE,
@@ -724,7 +724,7 @@
DBUS_TYPE_STRING,
&governor,
DBUS_TYPE_INVALID)) {
- char *gov2 = "userspace";
+ const char *gov2 = "userspace";
if (liblazy_dbus_system_send_method_call(DBUS_HAL_INTERFACE,
HAL_UDI_COMPUTER,
DBUS_HAL_CPUFREQ_INTERFACE,
@@ -1133,7 +1133,7 @@
}
}
if (CPU_ENABLE) {
- char *method = "CpufreqCPUEnable";
+ const char *method = "CpufreqCPUEnable";
err_code = liblazy_dbus_system_send_method_call(PS_DBUS_SERVICE,
PS_DBUS_PATH,
@@ -1168,7 +1168,7 @@
}
}
if (CPU_DISABLE) {
- char *method = "CpufreqCPUDisable";
+ const char *method = "CpufreqCPUDisable";
err_code = liblazy_dbus_system_send_method_call(PS_DBUS_SERVICE,
PS_DBUS_PATH,
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Remember to have fun...
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-commit+help@opensuse.org