On 08/15/2015 08:53 AM, Darshit Shah wrote:
I guess this issue is now closed? We should document libgpgme11-dev as a dependency.
Everything works OK here. Even without libgpgme-dev. Check out the attached patch. Regards, - AJ
>From 52ad32eb0846d19508974158bd26695d5dae8cc4 Mon Sep 17 00:00:00 2001 From: Ander Juaristi <[email protected]> Date: Mon, 17 Aug 2015 01:26:20 +0200 Subject: [PATCH] Documented Metalink dependencies --- README.checkout | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.checkout b/README.checkout index 03463d1..2d5af79 100644 --- a/README.checkout +++ b/README.checkout @@ -94,6 +94,10 @@ Compiling From Repository Sources saved the .pc file. Example: $ PKG_CONFIG_PATH="." ./configure + * [46]libmetalink and [47]GPGME are required for Metalink support. + If any of these are found by the ./configure script, it will still + succeed, but Wget will be compiled without Metalink support. + 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 +204,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/related_software/gpgme/ -- 1.9.1
