From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] rauc: bump to version 0.2
Date: Wed, 22 Nov 2017 09:49:26 +0100 [thread overview]
Message-ID: <20171122094926.17e557d2@windsurf.lan> (raw)
In-Reply-To: <20171122083709.lwprqlkpjcyzour3@sapphire.tkos.co.il>
Hello,
On Wed, 22 Nov 2017 10:37:10 +0200, Baruch Siach wrote:
> > If it's a runtime dependency...
> >
> > > -HOST_RAUC_DEPENDENCIES = host-pkgconf host-openssl host-libglib2
> > > +HOST_RAUC_DEPENDENCIES = host-pkgconf host-openssl host-libglib2 host-squashfs
> >
> > ...you don't need to list it in <pkg>_DEPENDENCIES.
>
> This is probably right in this case, since there is no in-tree host-rauc
> dependency. But in the general case a host package might be used at any point
> in the build. So you need to make sure that, e.g., host-squashfs is ready when
> host-rauc is to run, right?
Hum, you are right. I was thinking that host-rauc tools would be use
only in a post-image script, or after the build has finished. But
indeed, the tools can also be used by another package that depends on
host-rauc.
So: you're right, adding host-squashfs to <pkg>_DEPENDENCIES is needed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-22 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 4:31 [Buildroot] [PATCH] rauc: bump version to 0.2 Andrey Yurovsky
2017-11-22 4:17 ` [Buildroot] [PATCH v2] rauc: bump to version 0.2 Andrey Yurovsky
2017-11-22 7:53 ` Thomas Petazzoni
2017-11-22 8:37 ` Baruch Siach
2017-11-22 8:49 ` Thomas Petazzoni [this message]
2017-11-22 20:33 ` Thomas Petazzoni
2017-11-22 21:23 ` Andrey Yurovsky
2017-11-22 21:44 ` Thomas Petazzoni
2017-11-23 2:11 ` Andrey Yurovsky
2017-11-23 8:21 ` Thomas Petazzoni
2017-11-23 16:33 ` Andrey Yurovsky
2017-11-23 16:39 ` Thomas Petazzoni
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=20171122094926.17e557d2@windsurf.lan \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox