From f2cb6e050a28bb6c1e3a99a119360d4fd656fe62 Mon Sep 17 00:00:00 2001 From: Hubert Tarasiuk Date: Thu, 3 Sep 2015 20:40:21 -0700 Subject: [PATCH] Add information about libmetalink and GnuPG * README.checkout: Optional dependencies and URL references. --- README.checkout | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.checkout b/README.checkout index 03463d1e..3265c816 100644 --- a/README.checkout +++ b/README.checkout @@ -5,7 +5,8 @@ Compiling From Repository Sources normally present in the distribution tarballs. Therefore, to build GNU Wget from the sources in the repository, you'll need to have one or more of the following (note that gettext, OpenSSL, GnuTLS, libidn, - libiconv, libpsl, libpcre and pkg-config are not absolutely required): + libiconv, libpsl, libpcre, pkg-config, libmetalink and GnuPG are not + absolutely required): * [20]autoconf (currently, GNU Wget requires version 2.61). This is needed to generate the configure script from configure.in. This is @@ -94,6 +95,10 @@ Compiling From Repository Sources saved the .pc file. Example: $ PKG_CONFIG_PATH="." ./configure + * [46]libmetalink is needed to enable Metalink files support. + + * [47]GnuPG with GPGME is used to verify GPG-signed Metalink resources. + For those who might be confused as to what to do once they check out the source code, considering configure and Makefile do not yet exist at @@ -200,3 +205,5 @@ References 43. http://validator.w3.org/check?uri=referer 44. http://wget.addictivecode.org/WikiLicense 45. https://www.python.org/ + 46. https://launchpad.net/libmetalink + 47. https://www.gnupg.org