Initial import with numlockx 1.2 code

Author: rg3

AUTHORS

@@ -0,0 +1,2 @@
+Lubos Lunak <l.lunak@kde.org>
+XKB stuff by Oswald Buddenhagen <ossi@kde.org>

ChangeLog

@@ -0,0 +1,28 @@
+2010-03-13                L.Lunak <l.lunak@kde.org>
+	* 1.2
+        * autotools upgrade
+2005-10-03                L.Lunak <l.lunak@kde.org>
+	* 1.1
+        * toggle option from Chris Vanden Berghe <Chris@vandenberghe.org>
+        * autotools upgrade from Martin-Eric Racine <q-funk@iki.fi>
+2001-04-30                L.Lunak <l.lunak@kde.org>
+        * 1.0
+        * added XKB way of doing things from Oswald Buddenhagen <ossi@kde.org>
+        * removed distro specific portions
+2000-11-14                L.Lunak <l.lunak@email.cz>
+        * 0.3
+2000-08-30                L.Lunak <l.lunak@email.cz>
+        * added more X11 cfg. paths
+        * finally found out how to detect NumLock state without using XKB,
+            i.e. replaced the test from KLeds by my own test
+2000-06-28                L.Lunak <l.lunak@email.cz>
+        * added /usr/X11R6/lib/X11/xdm/Xsetup_0 and
+          /usr/X11R6/lib/X11/xinit/xinitrc as possible paths for X init files
+        * added 'make user_xinitrc'
+2000-06-14                L.Lunak <l.lunak@email.cz>
+        * 0.2 - added another ugly hack, so it's now possible to detect
+          NumLock state ( "borrowed" from KLeds
+          by Hans Matzen <hans@tm.informatik.uni-frankfurt.de> )
+        * added configure & Co.
+2000-02-18 ( or so )      L.Lunak <l.lunak@email.cz>
+        * 0.1 - first version, ugly hack to change NumLock state in X

INSTALL

@@ -0,0 +1,172 @@
+
+--------------------------------------------------------------
+ Please see README for package specific installation details.
+--------------------------------------------------------------
+
+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 a while.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Type `make install' to install the programs and any data files and
+     documentation.
+
+  4. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  
+
+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.
+
+   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.
+
+`--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.
+

LICENSE

@@ -0,0 +1,20 @@
+ Copyright (C) 2000-2001 Lubos Lunak        <l.lunak@kde.org>
+ Copyright (C) 2001      Oswald Buddenhagen <ossi@kde.org>
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
+THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.

Makefile.am

@@ -0,0 +1,128 @@
+# $Id: Makefile.am,v 1.8 2001/04/30 19:34:10 seli Exp $
+
+bin_PROGRAMS = numlockx
+
+numlockx_SOURCES = main.c 
+numlockx_LDADD   = @XTESTLIB@ -lXext -lX11 @X_PRE_LIBS@
+numlockx_LDFLAGS = @X_LDFLAGS@
+INCLUDES = @X_INCLUDES@
+
+CFLAGS = @CFLAGS@ -Wall -pedantic
+
+EXTRA_DIST = AUTHORS LICENSE ChangeLog INSTALL README TODO 
+
+AUTOMAKE_OPTIONS = foreign
+
+xsetup:
+	@if test -n "@xsetup@"; then \
+	    echo "Modifying @xsetup@"; \
+	    rm -f @xsetup@.tmp ;\
+	    cat @xsetup@ | grep -v "numlockx" > @xsetup@.tmp ;\
+	    echo "# Turn NumLock on ( numlockx ) ---------------" >> @xsetup@.tmp ;\
+	    echo "${bindir}/numlockx " >> @xsetup@.tmp ;\
+	    echo "# numlockx -----------------------------------" >> @xsetup@.tmp ;\
+	    cp -f @xsetup@ ${srcdir}/xsetup.sav ;\
+	    cat @xsetup@.tmp > @xsetup@ ;\
+	    rm -f @xsetup@.tmp; \
+	else \
+	    echo "Xsetup not found! - nothing to update";\
+	fi
+
+xsetup_uninstall:
+	@if test -n "@xsetup@"; then \
+	    echo "Restoring @xsetup@"; \
+	    rm -f @xsetup@.tmp ;\
+	    cat @xsetup@ | grep -v "numlockx" > @xsetup@.tmp ;\
+	    cat @xsetup@.tmp > @xsetup@ ;\
+	    rm -f @xsetup@.tmp; \
+	else \
+	    echo "Xsetup not found! - nothing to restore";\
+	fi
+
+xinitrc:
+	@if test -n "@xinitrc@"; then \
+	    echo "Modifying @xinitrc@"; \
+	    rm -f @xinitrc@.tmp ;\
+	    cat @xinitrc@ | grep -v "numlockx" \
+		| ( was_mod= ; \
+		    ifs_sav=$IFS ;\
+		    IFS= ;\
+		    while read ln; do \
+			if test -n "$$ln"; then \
+			    if test "$${ln#\#}" = "$$ln" ; then \
+				if test -z "$$was_mod"; then \
+			    	    was_mod=1 ;\
+			    	    echo "# Turn NumLock on ( numlockx ) ---------------";\
+			    	    echo "${bindir}/numlockx ";\
+				    echo "# numlockx -----------------------------------" ;\
+				fi \
+			    fi \
+			fi; \
+			echo "$$ln" ;\
+		    done; \
+		    IFS=$$ifs_sav ;\
+		    if test -z "$$was_mod"; then \
+		        was_mod=1 ;\
+		        echo "# Turn NumLock on ( numlockx ) ---------------";\
+		        echo "${bindir}/numlockx ";\
+			echo "# numlockx -----------------------------------" ;\
+		    fi \
+		  ) \
+		> @xinitrc@.tmp ;\
+	    cp -f @xinitrc@ ${srcdir}/xinitrc.sav ;\
+	    cat @xinitrc@.tmp > @xinitrc@ ;\
+	    rm -f @xinitrc@.tmp ;\
+	else \
+	    echo "xinitrc not found! - nothing to update";\
+	fi
+
+xinitrc_uninstall:
+	@if test -n "@xinitrc@"; then \
+	    echo "Restoring @xinitrc@"; \
+	    rm -f @xinitrc@.tmp ;\
+	    cat @xinitrc@ | grep -v "numlockx" > @xinitrc@.tmp ;\
+	    cat @xinitrc@.tmp > @xinitrc@ ;\
+	    rm -f @xinitrc@.tmp ;\
+	else \
+	    echo "xinitrc not found! - nothing to restore";\
+	fi
+
+user_xinitrc:
+	@if test -f ~/.xinitrc; then \
+	    echo "Modifying ~/.xinitrc"; \
+	    rm -f xinitrc.tmp ;\
+	    cat ~/.xinitrc | grep -v "numlockx" \
+		| ( was_mod= ; \
+		ifs_sav=$IFS ;\
+		IFS= ;\
+		while read ln; do \
+		    if test -n "$$ln"; then \
+			if test "$${ln#\#}" = "$$ln" ; then \
+			    if test -z "$$was_mod"; then \
+		    		was_mod=1 ;\
+		    		echo "# Turn NumLock on ( numlockx ) ---------------";\
+		    		echo "${bindir}/numlockx ";\
+				echo "# numlockx -----------------------------------" ;\
+			    fi \
+			fi \
+		    fi; \
+		    echo "$$ln" ;\
+		done; \
+		IFS=$$ifs_sav ;\
+		if test -z "$$was_mod"; then \
+	    	    was_mod=1 ;\
+	    	    echo "# Turn NumLock on ( numlockx ) ---------------";\
+	    	    echo "${bindir}/numlockx ";\
+		    echo "# numlockx -----------------------------------" ;\
+		fi \
+	          ) \
+		> xinitrc.tmp ;\
+		cp -f ~/.xinitrc ${srcdir}/xinitrc.sav ;\
+		cat xinitrc.tmp > ~/.xinitrc ;\
+		rm -f xinitrc.tmp ;\
+	else \
+	    echo "# Turn NumLock on ( numlockx ) ---------------" >> ~/.xinitrc; \
+	    echo "${bindir}/numlockx " >> ~/.xinitrc;\
+	    echo "# numlockx -----------------------------------" >> ~/.xinitrc;\
+	    chmod 700 ~/.xinitrc ; \
+	fi