From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wget: Depends on libuuid
Date: Tue, 1 Jul 2014 11:35:49 +0200 [thread overview]
Message-ID: <20140701113549.1d3f2569@free-electrons.com> (raw)
In-Reply-To: <1404206129-27696-1-git-send-email-a.potashev@geoscan.aero>
Dear Alexander Potashev,
On Tue, 1 Jul 2014 13:15:29 +0400, Alexander Potashev wrote:
> Signed-off-by: Alexander Potashev <a.potashev@geoscan.aero>
> ---
> package/wget/Config.in | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/package/wget/Config.in b/package/wget/Config.in
> index 26a2019..fc7ee26 100644
> --- a/package/wget/Config.in
> +++ b/package/wget/Config.in
> @@ -3,6 +3,8 @@ config BR2_PACKAGE_WGET
> # fork()
> depends on BR2_USE_MMU
> depends on BR2_USE_WCHAR
> + select BR2_PACKAGE_UTIL_LINUX
> + select BR2_PACKAGE_UTIL_LINUX_LIBUUID
> help
> Network utility to retrieve files from http, https and ftp.
I don't think libuuid is a mandatory dependency of wget, and if it was,
your patch would not be sufficient, because it does not add
'util-linux' to WGET_DEPENDENCIES.
However, it indeed seems to be a possible optional dependency of wget,
in which case what you want is the following addition in wget.mk:
ifeq ($(BR2_PACKAGE_UTIL_LINUX_LIBUUID),y)
WGET_DEPENDENCIES += util-linux
endif
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-01 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 9:15 [Buildroot] [PATCH] wget: Depends on libuuid Alexander Potashev
2014-07-01 9:32 ` Baruch Siach
2014-07-01 9:35 ` Thomas Petazzoni [this message]
[not found] ` <2414587.c08SQIiSAD@aspotashev>
2014-07-01 10:07 ` Baruch Siach
2014-07-01 10:12 ` Alexander Potashev
2014-07-01 11:29 ` Peter Korsgaard
2014-07-01 10:08 ` Alexander Potashev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140701113549.1d3f2569@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.