[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: gaf.git: branch: master updated (1.7.1-20110619-249-ged520a7)
The branch, master has been updated
via ed520a7824eef460c3924e064330ccef3696592e (commit)
via 0e506ebd5d5cc87a7f373b83b24f2ad3c90fd18b (commit)
via 6c0f45f324813ee0c1565f50c0a6e0a7debee9d8 (commit)
from a957588adee2ec54f0cc3c23f9650dff6ed03d09 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
=========
Summary
=========
docs/INSTALL | 229 --------------------------------------
docs/scheme-api/geda-scheme.texi | 3 +-
examples/INSTALL | 229 --------------------------------------
gattrib/INSTALL | 229 --------------------------------------
gattrib/Makefile.am | 3 +-
gnetlist/INSTALL | 100 -----------------
gschem/INSTALL | 123 --------------------
gsymcheck/INSTALL | 99 ----------------
libgeda/INSTALL | 124 --------------------
symbols/INSTALL | 19 ---
utils/INSTALL | 229 --------------------------------------
11 files changed, 2 insertions(+), 1385 deletions(-)
delete mode 100644 docs/INSTALL
delete mode 100644 examples/INSTALL
delete mode 100644 gattrib/INSTALL
delete mode 100644 gnetlist/INSTALL
delete mode 100644 gschem/FIXME
delete mode 100644 gschem/INSTALL
delete mode 100644 gsymcheck/INSTALL
delete mode 100644 libgeda/INSTALL
delete mode 100644 symbols/INSTALL
delete mode 100644 utils/INSTALL
=================
Commit Messages
=================
commit ed520a7824eef460c3924e064330ccef3696592e
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>
gschem: Remove empty FIXME file.
:100644 000000 e69de29... 0000000... D gschem/FIXME
commit 0e506ebd5d5cc87a7f373b83b24f2ad3c90fd18b
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>
Remove per-tool INSTALL files.
Only one top-level INSTALL file is needed, and that is provided by
automake.
:100644 000000 54caf7c... 0000000... D docs/INSTALL
:100644 000000 54caf7c... 0000000... D examples/INSTALL
:100644 000000 54caf7c... 0000000... D gattrib/INSTALL
:100644 100644 f5ec41a... c1625cb... M gattrib/Makefile.am
:100644 000000 b31b87c... 0000000... D gnetlist/INSTALL
:100644 000000 17444e2... 0000000... D gschem/INSTALL
:100644 000000 a6fcd51... 0000000... D gsymcheck/INSTALL
:100644 000000 6b50edb... 0000000... D libgeda/INSTALL
:100644 000000 4b42744... 0000000... D symbols/INSTALL
:100644 000000 54caf7c... 0000000... D utils/INSTALL
commit 6c0f45f324813ee0c1565f50c0a6e0a7debee9d8
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>
docs: Correct documentation for (user-data-dir).
:100644 100644 c451887... 2ac727e... M docs/scheme-api/geda-scheme.texi
=========
Changes
=========
commit ed520a7824eef460c3924e064330ccef3696592e
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>
gschem: Remove empty FIXME file.
diff --git a/gschem/FIXME b/gschem/FIXME
deleted file mode 100644
index e69de29..0000000
commit 0e506ebd5d5cc87a7f373b83b24f2ad3c90fd18b
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>
Remove per-tool INSTALL files.
Only one top-level INSTALL file is needed, and that is provided by
automake.
diff --git a/docs/INSTALL b/docs/INSTALL
deleted file mode 100644
index 54caf7c..0000000
--- a/docs/INSTALL
+++ /dev/null
@@ -1,229 +0,0 @@
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 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' 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' 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 `--target=TYPE' option 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
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`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/examples/INSTALL b/examples/INSTALL
deleted file mode 100644
index 54caf7c..0000000
--- a/examples/INSTALL
+++ /dev/null
@@ -1,229 +0,0 @@
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 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' 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' 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 `--target=TYPE' option 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
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`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/gattrib/INSTALL b/gattrib/INSTALL
deleted file mode 100644
index 54caf7c..0000000
--- a/gattrib/INSTALL
+++ /dev/null
@@ -1,229 +0,0 @@
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 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' 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' 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 `--target=TYPE' option 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
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`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/gattrib/Makefile.am b/gattrib/Makefile.am
index f5ec41a..c1625cb 100644
--- a/gattrib/Makefile.am
+++ b/gattrib/Makefile.am
@@ -1,7 +1,6 @@
SUBDIRS = po src include lib design docs data
-EXTRA_DIST = BUGS NOTES README ChangeLog ChangeLog-1.0 \
- INSTALL ToDos
+EXTRA_DIST = BUGS NOTES README ChangeLog ChangeLog-1.0 ToDos
if HAVE_GIT_REPO
ChangeLog: $(top_builddir)/stamp-git
diff --git a/gnetlist/INSTALL b/gnetlist/INSTALL
deleted file mode 100644
index b31b87c..0000000
--- a/gnetlist/INSTALL
+++ /dev/null
@@ -1,100 +0,0 @@
-gEDA
-
-GPL Electronic Design Automation
-------------------------------------------------------------------------------
-
-Installation instructions
-
-Please see the end of this file for platform / vendor specific hints and
-tips.
-
------------------------------------------------------------------------------
-Quick Ref:
-
-% ./configure
-% make
-% make install
-
-In order to build gschem you must install the following packages first:
-
- GLIB 1.2.x
- GTK+ 1.2.x
- guile 1.4.x or 1.6.x
- libgeda
- symbols
- LibStroke 0.5.1 (optional)
-
------------------------------------------------------------------------------
-More detailed info:
-
-
- First run the configure script in the toplevel directory of gnetlist:
-
- ./configure (This should guess everything right)
- (e-mail me if it doesn't)
- make all
-
- Run: configure --help for more options (such as overriding the default
- prefix).
-
- You can specify where rc files are installed by using the --with-rcdir=path
- when you run ./configure. This is useful to package maintainers who would
- like to override where gschem and friends search for the rc files.
-
-- To install gnetlist into the prefix dir (and subdirs) type:
-
- make install
-
- in gschem's top level directory
-
-
-gEDA uses GNU Libtool in order to build shared libraries on a
-variety of systems. While this is very nice for making usable
-binaries, it can be a pain when trying to debug a program. For that
-reason, compilation of shared libraries can be turned off by
-specifying the `--disable-shared' option to `configure'.
-
-The configure script should figure out most system dependant things, but at
-this point I'm either not taking into account what configure figures out or
-I have missed some system dependence. So please e-mail me at:
-ahvezda@xxxxxxxxxxxxx
-
-- Uninstall
-
- To uninstall a previous version (or the current version) of gEDA type:
-
- make uninstall
-
- in the top level gEDA source directory. This will remove installed files
- which belong to gEDA.
-
-
-Platform / Vendor specific tips and hints
-------------------------------------------
-
-- libc5 (SuSE)
-
- If you get the following error message:
-
- "link: '-L' cannot specify a relative directory"
-
- There is a problem with readline and guile. Please hide (rename)
- libreadline.so.* (move it out of wherever it is installed) and rebuild
- guile again. Then recompile gEDA and things should work right.
-
-- Redhat 6.0
-
- The guile RPMs that are shipped with RedHat 6.0 has been giving some
- people some trouble. The solution seems to grab either the SRPMS and
- build that or get the guile-1.3.tar.gz file and build guile manually.
-
-- SunOS / Solaris
-
- If you have problems running the shell script wrappers (when
- running ./gschem or any of the other programs), try changing
- the shell to /bin/ksh (or where ksh is). /bin/sh is known to
- be of lesser quality on Solaris.
-
- Also run ./configure --disable-shared if you have to problems
- running programs because a shared library isn't be found/loaded.
-
diff --git a/gschem/INSTALL b/gschem/INSTALL
deleted file mode 100644
index 17444e2..0000000
--- a/gschem/INSTALL
+++ /dev/null
@@ -1,123 +0,0 @@
-gEDA
-
-GPL Electronic Design Automation
-------------------------------------------------------------------------------
-
-Installation instructions
-
-Please see the end of this file for platform / vendor specific hints and
-tips. Also please read the README file in this same directory.
-
------------------------------------------------------------------------------
-Quick Ref:
-
-% ./configure
-% make
-% make install
-
-In order to build gschem you must install the following packages first:
-
- GLIB 2.4.x
- GTK+ 2.4.x and all dependancies
- guile 1.6.x or later
- libgeda (match version and must be installed first)
- symbols
- LibStroke 0.5.1 (optional)
-
------------------------------------------------------------------------------
-More detailed info:
-
-- To compile gschem with gtk+ installed in some system directory (/usr/local
- for example) type:
-
-
- ./configure (This should guess everything right)
- (e-mail me if it doesn't)
- make all
-
- Run: configure --help for more options (such as overriding the default
- prefix).
-
- You can specify where rc files are installed by using the --with-rcdir=path
- when you run ./configure. This is useful to package maintainers who would
- like to override where gschem and friends search for the rc files.
-
-- To install gschem into the prefix dir (and subdirs) type:
-
- make install
-
- in gschem's top level directory
-
-
-gEDA uses GNU Libtool in order to build shared libraries on a
-variety of systems. While this is very nice for making usable
-binaries, it can be a pain when trying to debug a program. For that
-reason, compilation of shared libraries can be turned off by
-specifying the `--disable-shared' option to `configure'.
-
-The configure script should figure out most system dependant things, but at
-this point I'm either not taking into account what configure figures out or
-I have missed some system dependance. So please e-mail me at:
-ahvezda@xxxxxxxxxxxxx
-
-
-- Disabling strokes
-
- If configure finds libstroke installed it will automatically enable
- stroke support. To disable this run configure like:
-
- ./configure --disable-strokes
-
- Then do:
-
- make clean
- make all
-
-
-- Uninstall
-
- To uninstall a previous version (or the current version) of gEDA type:
-
- make uninstall
-
- in the top level gEDA source directory. This will remove installed files
- which belong to gEDA.
-
-
-Platform / Vendor specific tips and hints
-------------------------------------------
-
-- libc5 (SuSE)
-
- If you get the following error message:
-
- "link: '-L' cannot specify a relative directory"
-
- There is a problem with readline and guile. Please hide (rename)
- libreadline.so.* (move it out of wherever it is installed) and rebuild
- guile again. Then recompile gEDA and things should work right.
-
-- Redhat 6.0
-
- The guile RPMs that are shipped with RedHat 6.0 has been giving some
- people some trouble. The solution seems to grab either the SRPMS and
- build that or get the guile-1.3.tar.gz file and build guile manually.
-
-- libstroke
-
- Be sure you do not compile libstroke with MOUSE_DROPPINGS defined;
- it won't work at all with gschem. You would have had to manually
- define MOUSE_DROPPINGS, so if you just followed the build
- instructions you should be okay.
-
-
-- SunOS / Solaris
-
- If you have problems running the shell script wrappers (when
- running ./gschem or any of the other programs), try changing
- the shell to /bin/ksh (or where ksh is). /bin/sh is known to
- be of lesser quality on Solaris.
-
- Also run ./configure --disable-shared if you have to problems
- running programs because a shared library isn't be found/loaded.
-
diff --git a/gsymcheck/INSTALL b/gsymcheck/INSTALL
deleted file mode 100644
index a6fcd51..0000000
--- a/gsymcheck/INSTALL
+++ /dev/null
@@ -1,99 +0,0 @@
-gEDA
-
-GPL Electronic Design Automation
-------------------------------------------------------------------------------
-
-Installation instructions
-
-Please see the end of this file for platform / vendor specific hints and
-tips.
-
------------------------------------------------------------------------------
-Quick Ref:
-
-% ./configure
-% make
-% make install
-
-In order to build gschem you must install the following packages first:
-
- GLIB 1.2.x
- GTK+ 1.2.x
- libgeda
- symbols
- LibStroke 0.5.1 (optional)
-
------------------------------------------------------------------------------
-More detailed info:
-
-
- First run the configure script in the toplevel directory of gnetlist:
-
- ./configure (This should guess everything right)
- (e-mail me if it doesn't)
- make all
-
- Run: configure --help for more options (such as overriding the default
- prefix).
-
- You can specify where rc files are installed by using the --with-rcdir=path
- when you run ./configure. This is useful to package maintainers who would
- like to override where gschem and friends search for the rc files.
-
-- To install gnetlist into the prefix dir (and subdirs) type:
-
- make install
-
- in gschem's top level directory
-
-
-gEDA uses GNU Libtool in order to build shared libraries on a
-variety of systems. While this is very nice for making usable
-binaries, it can be a pain when trying to debug a program. For that
-reason, compilation of shared libraries can be turned off by
-specifying the `--disable-shared' option to `configure'.
-
-The configure script should figure out most system dependant things, but at
-this point I'm either not taking into account what configure figures out or
-I have missed some system dependance. So please e-mail me at:
-ahvezda@xxxxxxxxxxxxx
-
-- Uninstall
-
- To uninstall a previous version (or the current version) of gEDA type:
-
- make uninstall
-
- in the top level gEDA source directory. This will remove installed files
- which belong to gEDA.
-
-
-Platform / Vendor specific tips and hints
-------------------------------------------
-
-- libc5 (SuSE)
-
- If you get the following error message:
-
- "link: '-L' cannot specify a relative directory"
-
- There is a problem with readline and guile. Please hide (rename)
- libreadline.so.* (move it out of wherever it is installed) and rebuild
- guile again. Then recompile gEDA and things should work right.
-
-- Redhat 6.0
-
- The guile RPMs that are shipped with RedHat 6.0 has been giving some
- people some trouble. The solution seems to grab either the SRPMS and
- build that or get the guile-1.3.tar.gz file and build guile manually.
-
-- SunOS / Solaris
-
- If you have problems running the shell script wrappers (when
- running ./gschem or any of the other programs), try changing
- the shell to /bin/ksh (or where ksh is). /bin/sh is known to
- be of lesser quality on Solaris.
-
- Also run ./configure --disable-shared if you have to problems
- running programs because a shared library isn't be found/loaded.
-
diff --git a/libgeda/INSTALL b/libgeda/INSTALL
deleted file mode 100644
index 6b50edb..0000000
--- a/libgeda/INSTALL
+++ /dev/null
@@ -1,124 +0,0 @@
-gEDA
-
-GPL Electronic Design Automation
-------------------------------------------------------------------------------
-
-Installation instructions
-
-Please see the end of this file for platform / vendor specific hints and
-tips. Also please read the README file in this same directory.
-
------------------------------------------------------------------------------
-Quick Ref:
-
-% ./configure
-% make
-% make install
-
-(Depending on where you installed the libraries, you might have to run
- ldconfig (as root)).
-
-In order to build libgeda you must install the following packages first:
-
- GLIB 2.4.x
- GTK+ 2.4.x and all dependancies
- guile 1.6.x or later
- LibStroke 0.5.1 (optional)
-
------------------------------------------------------------------------------
-More detailed info:
-
-- To compile libgeda with gtk+ installed in some system directory (/usr/local
- for example) type:
-
-
- ./configure (This should guess everything right)
- (e-mail me if it doesn't)
- make all
-
- Run: configure --help for more options (such as overriding the default
- prefix).
-
-- To install libgeda into the prefix dir (and subdirs) type:
-
- make install
-
- in libgeda's top level directory
-
-
-gEDA uses GNU Libtool in order to build shared libraries on a
-variety of systems. While this is very nice for making usable
-binaries, it can be a pain when trying to debug a program. For that
-reason, compilation of shared libraries can be turned off by
-specifying the `--disable-shared' option to `configure'.
-
-The configure script should figure out most system dependant things, but at
-this point I'm either not taking into account what configure figures out or
-I have missed some system dependance. So please e-mail me at:
-ahvezda@xxxxxxxxxxxxx
-
-
-- Disabling strokes
-
- If configure finds libstroke installed it will automatically enable
- stroke support. To disable this run configure like:
-
- ./configure --disable-strokes
-
- Then do:
-
- make clean
- make all
-
-
-- Uninstall
-
- To uninstall a previous version (or the current version) of gEDA type:
-
- make uninstall
-
- in the top level gEDA source directory. This will remove installed files
- which belong to gEDA.
-
-
-Platform / Vendor specific tips and hints
-------------------------------------------
-
-- libc5 (SuSE)
-
- If you get the following error message:
-
- "link: '-L' cannot specify a relative directory"
-
- There is a problem with readline and guile. Please hide (rename)
- libreadline.so.* (move it out of wherever it is installed) and rebuild
- guile again. Then recompile gEDA and things should work right.
-
-- Redhat 6.0
-
- The guile RPMs that are shipped with RedHat 6.0 has been giving some
- people some trouble. The solution seems to grab either the SRPMS and
- build that or get the guile-1.3.tar.gz file and build guile manually.
-
- It is important to install *-devel rpms for the various packages
- which gEDA depends upon. gEDA will not build without them being
- installed.
-
-- libstroke
-
- Be sure you do not compile libstroke with MOUSE_DROPPINGS defined;
- it won't work at all with gschem. You would have had to manually
- define MOUSE_DROPPINGS, so if you just followed the build
- instructions you should be okay.
-
-
-- SunOS / Solaris
-
- If you have problems running the shell script wrappers (when
- running ./gschem or any of the other programs), try changing
- the shell to /bin/ksh (or where ksh is). /bin/sh is known to
- be of lesser quality on Solaris.
-
- Also run ./configure --disable-shared if you have to problems
- running programs because a shared library isn't be found/loaded.
-
diff --git a/symbols/INSTALL b/symbols/INSTALL
deleted file mode 100644
index 4b42744..0000000
--- a/symbols/INSTALL
+++ /dev/null
@@ -1,19 +0,0 @@
-gEDA
-
-GPL Electronic Design Automation
-------------------------------------------------------------------------------
-
-Installation instructions
-
-Please see the end of this file for platform / vendor specific hints and
-tips.
-
-
------------------------------------------------------------------------------
-Quick Ref:
-
-% ./configure
-% make install
-
-There is no code to build in this package.
-
diff --git a/utils/INSTALL b/utils/INSTALL
deleted file mode 100644
index 54caf7c..0000000
--- a/utils/INSTALL
+++ /dev/null
@@ -1,229 +0,0 @@
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 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' 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' 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 `--target=TYPE' option 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
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`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.
-
commit 6c0f45f324813ee0c1565f50c0a6e0a7debee9d8
Author: Peter TB Brett <peter@xxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>
docs: Correct documentation for (user-data-dir).
diff --git a/docs/scheme-api/geda-scheme.texi b/docs/scheme-api/geda-scheme.texi
index c451887..2ac727e 100644
--- a/docs/scheme-api/geda-scheme.texi
+++ b/docs/scheme-api/geda-scheme.texi
@@ -1633,8 +1633,7 @@ gEDA configuration information.
@end defun
@defun user-data-dir
-Returns an ordered list of directories in which to store user-specific
-gEDA data.
+Returns the directory in which to store user-specific gEDA data.
@end defun
@defun user-config-dir
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs