From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wget: Depends on libuuid
Date: Tue, 1 Jul 2014 13:07:27 +0300 [thread overview]
Message-ID: <20140701100727.GN4425@tarshish> (raw)
In-Reply-To: <2414587.c08SQIiSAD@aspotashev>
Hi Alexander,
On Tue, Jul 01, 2014 at 01:55:35PM +0400, Alexander Potashev wrote:
> ? ?????? ?? 1 ???? 2014 11:35:49 ???????????? Thomas Petazzoni ???????:
> > 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
>
> Looks good, although one could argue if keeping *_DEPENDENCIES up-to-date is
> important when we also have dependency assurance in Config.in.
No. These are two different levels of dependencies. Config.in 'select'
determines which packages are to be built. You need this for mandatory
dependencies. The per package $(PKG)_DEPENDENCIES determines the ORDER of the
build. $(PKG)_DEPENDENCIES should list both mandatory AND optional
dependencies to get a reproducible result.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-07-01 10:07 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
[not found] ` <2414587.c08SQIiSAD@aspotashev>
2014-07-01 10:07 ` Baruch Siach [this message]
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=20140701100727.GN4425@tarshish \
--to=baruch@tkos.co.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox