Source-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[src/trunk]: src/external/bsd/atf/dist Remove unnecessary files
details: https://anonhg.NetBSD.org/src/rev/0d792dcbb2b0
branches: trunk
changeset: 755744:0d792dcbb2b0
user: jmmv <jmmv%NetBSD.org@localhost>
date: Fri Jun 18 15:41:20 2010 +0000
description:
Remove unnecessary files
The just-commited prepare-import.sh script will take care of spotting extra
files that may be unnecessary during a future import.
diffstat:
external/bsd/atf/dist/INSTALL | 340 -
external/bsd/atf/dist/Makefile.am | 1820 -
external/bsd/atf/dist/Makefile.am.m4 | 1083 -
external/bsd/atf/dist/Makefile.in | 6117 ----
external/bsd/atf/dist/aclocal.m4 | 1002 -
external/bsd/atf/dist/admin/check-install.sh | 92 -
external/bsd/atf/dist/admin/check-style-c.awk | 94 -
external/bsd/atf/dist/admin/check-style-common.awk | 82 -
external/bsd/atf/dist/admin/check-style-cpp.awk | 86 -
external/bsd/atf/dist/admin/check-style-man.awk | 78 -
external/bsd/atf/dist/admin/check-style-shell.awk | 106 -
external/bsd/atf/dist/admin/check-style.sh | 187 -
external/bsd/atf/dist/admin/choose-revision.sh | 74 -
external/bsd/atf/dist/admin/compile | 143 -
external/bsd/atf/dist/admin/config.guess | 1502 -
external/bsd/atf/dist/admin/config.sub | 1708 -
external/bsd/atf/dist/admin/depcomp | 630 -
external/bsd/atf/dist/admin/generate-makefile.sh | 75 -
external/bsd/atf/dist/admin/generate-revision-dist.sh | 107 -
external/bsd/atf/dist/admin/generate-revision.sh | 166 -
external/bsd/atf/dist/admin/install-sh | 291 -
external/bsd/atf/dist/admin/ltmain.sh | 8406 ------
external/bsd/atf/dist/admin/missing | 376 -
external/bsd/atf/dist/bconfig.h.in | 119 -
external/bsd/atf/dist/configure | 19038 --------------
external/bsd/atf/dist/configure.ac | 221 -
external/bsd/atf/dist/doc/authors.xml | 50 -
external/bsd/atf/dist/doc/build-xml.sh | 206 -
external/bsd/atf/dist/doc/copying.xml | 114 -
external/bsd/atf/dist/doc/install.xml | 503 -
external/bsd/atf/dist/doc/news.xml | 370 -
external/bsd/atf/dist/doc/readme.xml | 74 -
external/bsd/atf/dist/doc/specification.xml | 692 -
external/bsd/atf/dist/doc/standalone/authors.html | 71 -
external/bsd/atf/dist/doc/standalone/copying.html | 169 -
external/bsd/atf/dist/doc/standalone/install.html | 694 -
external/bsd/atf/dist/doc/standalone/news.html | 620 -
external/bsd/atf/dist/doc/standalone/readme.html | 108 -
external/bsd/atf/dist/doc/standalone/sdocbook.xsl | 278 -
external/bsd/atf/dist/doc/standalone/specification.html | 1096 -
external/bsd/atf/dist/doc/standalone/standalone.css | 93 -
external/bsd/atf/dist/doc/text/authors.txt | 27 -
external/bsd/atf/dist/doc/text/copying.txt | 70 -
external/bsd/atf/dist/doc/text/install.txt | 340 -
external/bsd/atf/dist/doc/text/news.txt | 284 -
external/bsd/atf/dist/doc/text/readme.txt | 46 -
external/bsd/atf/dist/doc/text/specification.txt | 562 -
external/bsd/atf/dist/m4/compiler-flags.m4 | 110 -
external/bsd/atf/dist/m4/cxx-std-funcs.m4 | 83 -
external/bsd/atf/dist/m4/developer-mode.m4 | 97 -
external/bsd/atf/dist/m4/doc-build.m4 | 120 -
external/bsd/atf/dist/m4/libtool.m4 | 7357 -----
external/bsd/atf/dist/m4/ltoptions.m4 | 368 -
external/bsd/atf/dist/m4/ltsugar.m4 | 123 -
external/bsd/atf/dist/m4/ltversion.m4 | 23 -
external/bsd/atf/dist/m4/lt~obsolete.m4 | 92 -
external/bsd/atf/dist/m4/module-application.m4 | 77 -
external/bsd/atf/dist/m4/module-defs.m4 | 53 -
external/bsd/atf/dist/m4/module-env.m4 | 36 -
external/bsd/atf/dist/m4/module-fs.m4 | 77 -
external/bsd/atf/dist/m4/module-sanity.m4 | 32 -
external/bsd/atf/dist/m4/module-signals.m4 | 92 -
external/bsd/atf/dist/m4/runtime-tool.m4 | 44 -
63 files changed, 0 insertions(+), 59194 deletions(-)
diffs (truncated from 59446 to 300 lines):
diff -r 261c367f0502 -r 0d792dcbb2b0 external/bsd/atf/dist/INSTALL
--- a/external/bsd/atf/dist/INSTALL Fri Jun 18 15:39:17 2010 +0000
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,340 +0,0 @@
- Installation instructions
-
- By Julio Merino, The NetBSD Foundation
-
- Contents
-
- 1. Introduction
-
- 2. Dependencies
-
- 3. Regenerating the build system
-
- 4. General build procedure
-
- 5. Configuration flags
-
- 6. Post-installation steps
-
- Introduction
-
- ATF uses the GNU Automake, GNU Autoconf and GNU Libtool utilities as its
- build system. These are used only when compiling the application from the
- source code package. If you want to install ATF from a binary package, you
- do not need to read this document.
-
- For the impatient:
-
- $ ./configure
- $ make
- Gain root privileges
- # make install
- Drop root privileges
- $ make installcheck
-
- Or alternatively, install as a regular user into your home directory:
-
- $ ./configure --prefix ~/local
- $ make
- $ make install
- $ make installcheck
-
- Dependencies
-
- To build and use ATF successfully you need:
-
- * A standards-compliant C/C++ complier. For example, GNU GCC 2.95 will
- not work.
-
- * A POSIX shell interpreter.
-
- * A make(1) utility.
-
- If you are building ATF from the code on the repository, you will also
- need the following tools. The versions listed here are the ones used to
- build the files bundled in the last formal release, but these are not
- strictly required. Newer ones will most likely work and, maybe, some
- slightly older ones:
-
- * GNU autoconf 2.65
-
- * GNU automake 1.11.1
-
- * GNU libtool 2.2.6b
-
- If you are building the XML documentation (which is a requisite to be able
- to generate a distfile), you will also need the following tools:
-
- * links
-
- * The Simple DocBook DTD 1.1
-
- * tidy
-
- * xsltproc
-
- * xmlcatalog and xmllint
-
- Regenerating the build system
-
- If you are building ATF from code extracted from the repository, you must
- first regenerate the files used by the build system. You will also need to
- do this if you modify one of configure.ac or Makefile.am.m4. To do this,
- simply run:
-
- $ ./autogen.sh
-
- For formal releases, no extra steps are needed.
-
- General build procedure
-
- To build and install the source package, you must follow these steps:
-
- 1. Configure the sources to adapt to your operating system. This is done
- using the 'configure' script located on the sources' top directory,
- and it is usually invoked without arguments unless you want to change
- the installation prefix. More details on this procedure are given on a
- later section.
-
- 2. Build the sources to generate the binaries and scripts. Simply run
- 'make' on the sources' top directory after configuring them. No
- problems should arise.
-
- 3. Install the program by running 'make install'. You may need to become
- root to issue this step.
-
- 4. Issue any manual installation steps that may be required. These are
- described later in their own section.
-
- 5. Check that the installed programs work by running 'make installcheck'.
- You do not need to be root to do this, even though some checks will
- not be run otherwise.
-
- Configuration flags
-
- The most common, standard flags given to 'configure' are:
-
- * --prefix=directory
-
- Possible values: Any path
-
- Default: /usr/local
-
- Specifies where the program (binaries and all associated files) will
- be installed.
-
- * --sysconfdir=directory
-
- Possible values: Any path
-
- Default: /usr/local/etc
-
- Specifies where the installed programs will look for configuration
- files. '/atf' will be appended to the given path unless ATF_CONFSUBDIR
- is redefined as explained later on.
-
- * --help
-
- Shows information about all available flags and exits immediately,
- without running any configuration tasks.
-
- The following environment variables are specific to ATF's 'configure'
- script:
-
- * ATF_BUILD_CC
-
- Possible values: empty, a absolute or relative path to a C compiler.
-
- Default: the value of CC as detected by the configure script.
-
- Specifies the C compiler that ATF will use at run time whenever the
- build-time-specific checks are used.
-
- * ATF_BUILD_CFLAGS
-
- Possible values: empty, a list of valid C compiler flags.
-
- Default: the value of CFLAGS as detected by the configure script.
-
- Specifies the C compiler flags that ATF will use at run time whenever
- the build-time-specific checks are used.
-
- * ATF_BUILD_CPP
-
- Possible values: empty, a absolute or relative path to a C/C++
- preprocessor.
-
- Default: the value of CPP as detected by the configure script.
-
- Specifies the C/C++ preprocessor that ATF will use at run time
- whenever the build-time-specific checks are used.
-
- * ATF_BUILD_CPPFLAGS
-
- Possible values: empty, a list of valid C/C++ preprocessor flags.
-
- Default: the value of CPPFLAGS as detected by the configure script.
-
- Specifies the C/C++ preprocessor flags that ATF will use at run time
- whenever the build-time-specific checks are used.
-
- * ATF_BUILD_CXX
-
- Possible values: empty, a absolute or relative path to a C++ compiler.
-
- Default: the value of CXX as detected by the configure script.
-
- Specifies the C++ compiler that ATF will use at run time whenever the
- build-time-specific checks are used.
-
- * ATF_BUILD_CXXFLAGS
-
- Possible values: empty, a list of valid C++ compiler flags.
-
- Default: the value of CXXFLAGS as detected by the configure script.
-
- Specifies the C++ compiler flags that ATF will use at run time
- whenever the build-time-specific checks are used.
-
- * ATF_CONFSUBDIR
-
- Possible values: empty, a relative path.
-
- Default: atf.
-
- Specifies the subdirectory of the configuration directory (given by
- the --sysconfdir argument) under which ATF will search for its
- configuration files.
-
- * ATF_M4
-
- Possible values: empty, absolute path to a M4 macro processor.
-
- Default: empty.
-
- Specifies the M4 macro processor that ATF will use at run time to
- generate GNU Automake files. If empty, the configure script will try
- to find a suitable M4 implementation for you.
-
- * ATF_SHELL
-
- Possible values: empty, absolute path to a POSIX shell interpreter.
-
- Default: empty.
-
- Specifies the POSIX shell interpreter that ATF will use at run time to
- execute its scripts and the test programs written using the atf-sh
- library. If empty, the configure script will try to find a suitable
- interpreter for you.
-
- * ATF_WORKDIR
-
- Possible values: empty, an absolute path.
-
- Default: /tmp or /var/tmp, depending on availability.
-
- Specifies the directory that ATF will use to place its temporary files
- and work directories for test cases. This is just a default and can be
- overriden at run time.
-
- * LINKS
-
- Possible values: absolute path.
-
- Default: links.
-
- Specifies the program name or the absolute path of the 'links'
- application. Required when --enable-doc-build is used; otherwise
- ignored.
-
- * TIDY
-
- Possible values: absolute path.
-
- Default: tidy.
-
- Specifies the program name or the absolute path of the 'tidy' tool.
- Required when --enable-doc-build is used; otherwise ignored.
-
- * XMLCATALOG
-
- Possible values: absolute path.
-
- Default: xmlcatalog.
-
- Specifies the program name or the absolute path of the 'xmlcatalog'
- tool. Required when --enable-doc-build is used; otherwise ignored.
-
- * XML_CATALOG_FILE
-
- Possible values: absolute path.
-
- Default: /etc/xml/catalog
-
- Specifies the path to the system-wide XML catalog used to lookup the
- required DTDs. The build will NOT perform any network access to load
- them. Required when --enable-doc-build is used; otherwise ignored.
-
- * XMLLINT
-
- Possible values: absolute path.
-
- Default: xmllint.
-
- Specifies the program name or the absolute path of the 'xmllint' tool.
- Required when --enable-doc-build is used; otherwise ignored.
-
- * XSLTPROC
-
- Possible values: absolute path.
-
- Default: xsltproc.
-
- Specifies the program name or the absolute path of the 'xsltproc'
- tool. Required when --enable-doc-build is used; otherwise ignored.
-
- The following flags are specific to ATF's 'configure' script:
Home |
Main Index |
Thread Index |
Old Index