aboutsummaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>2006-11-30 15:36:39 +0000
committerWerner Koch <[email protected]>2006-11-30 15:36:39 +0000
commit85bb107c10d6f9c3eb8f2b93e047588b3f77a666 (patch)
tree052e65b56e2eaec0d2ce7fbe521e428a08ba13ed /README
parentRemoved included gettext and updated latest gettext (diff)
downloadlibgpg-error-1.5.tar.gz
libgpg-error-1.5.zip
* configure.ac: Set LT version to C3/A3/R1.libgpg-error-1.5
* README: Switch to tar.bz2 and sha1sum. * src/gpg-error.c (main): Add option --version. * autogen.sh (FORCE): Add option --force. * intl/: Removed. * Makefile.am (SUBDIRS): Removed intl. * configure.ac (AM_GNU_GETTEXT): Use external flag * src/Makefile.am: Removed -I../intl.
Diffstat (limited to '')
-rw-r--r--README14
-rw-r--r--README.SVN (renamed from README.CVS)43
2 files changed, 29 insertions, 28 deletions
diff --git a/README b/README
index 2c11c9a..04a48dc 100644
--- a/README
+++ b/README
@@ -32,7 +32,7 @@ Here is a quick summary:
important step!
2) Unpack the archive. With GNU tar you can do it this way:
- "tar xzvf libgpg-error-x.y.tar.gz"
+ "tar xjvf libgpg-error-x.y.tar.bz2"
3) "cd libgpg-error-x.y"
@@ -53,24 +53,24 @@ do it in one of the following ways:
a) If you already have a trusted version of GnuPG installed, you can
simply check the supplied signature:
- $ gpg --verify libgpg-error-x.y.tar.gz.sig
+ $ gpg --verify libgpg-error-x.y.tar.bz2.sig
- This checks that the detached signature libgpg-error-x.y.tar.gz.sig
- is indeed a a signature of libgpg-error-x.y.tar.gz.
+ This checks that the detached signature libgpg-error-x.y.tar.bz2.sig
+ is indeed a a signature of libgpg-error-x.y.tar.bz2.
Please note that you have to use an old version of GnuPG to do all
this stuff. *Never* use the version which was built using the
library you are trying to verify!
b) If you don't have any a trusted version of GnuPG, you can attempt
- to verify the MD5 checksum, using a trusted version of the md5sum
+ to verify the SHA1 checksum, using a trusted version of the sha1sum
program:
- $ md5sum libgpg-error-x.y.tar.gz
+ $ sha1sum libgpg-error-x.y.tar.bz2
This should yield an output _similar_ to this:
- fd9351b26b3189c1d577f0970f9dcadc libgpg-error-x.y.tar.gz
+ 610064e5b77700f5771c8fde2691c4365e1ca100 libgpg-error-x.y.tar.bz2
Now check that this checksum is _exactly_ the same as the one
published via the announcement list and probably via Usenet.
diff --git a/README.CVS b/README.SVN
index 3fd9b5f..c642282 100644
--- a/README.CVS
+++ b/README.SVN
@@ -1,18 +1,19 @@
-If you are building from CVS, run the script
+If you are building from Subversion, run the script
-$ ./autogen.sh
+./autogen.sh
-to make sure that all the necessary maintainer tools are installed and
-to build the actual configuration files. Then run
+first, to make sure that you have all the necessary maintainer tools
+are installed and to build the actual configuration files. If you
+have just updated from SVN, you should add the option "--force" to
+autogen.sh so that meta data from SVN is noticed. Then run
-$ ./configure --enable-maintainer-mode
+./configure --enable-maintainer-mode
followed by the usual make.
-
If autogen.sh complains about insufficient versions of the required
-tools, or the tools are not installed in the default location, you may
-use environment variables to override the default tool names:
+tools, or the tools are not installed, you may use environment
+variables to override the default tool names:
AUTOMAKE_SUFFIX is used as a suffix for all tools from the automake
package. For example
@@ -24,27 +25,27 @@ use environment variables to override the default tool names:
uses "automake" and "aclocal" in the /usr/foo/bin
directory.
AUTOCONF_SUFFIX is used as a suffix for all tools from the automake
- package.
+ package
AUTOCONF_PREFIX is used as a prefix for all tools from the automake
- package.
+ package
GETTEXT_SUFFIX is used as a suffix for all tools from the gettext
- package.
+ package
GETTEXT_PREFIX is used as a prefix for all tools from the gettext
- package.
-
+ package
It is also possible to use the variable name AUTOMAKE, AUTOCONF,
ACLOCAL, AUTOHEADER, GETTEXT and MSGMERGE to directly specify the name
of the programs to run. It is however better to use the suffix and
-prefix forms as described above, because that does not require
-knowledge about the actual tools used by autogen.sh.
+prefix forms as described above because that does not require
+knowledge about the actual tools used by autgen.sh.
Please don't use autopoint, libtoolize or autoreconf unless you are
the current maintainer and want to update the standard configuration
-files. All the files generated from these tools should be in the
-repository and only updated manually if the maintainer decides that
-newer versions are required. The maintainer should also make sure
-that the required version of automake et al. are properly indicated at
-the top of configure.ac and take care to copy the files and not merely
-use symlinks.
+files. All those files should be in the SVN and only updated manually
+if the maintainer decides that newer versions are required. The
+maintainer should also make sure that the required version of automake
+et al. are properly indicated at the top of configure.ac and take care
+to copy the files and not merely use symlinks.
+
+