From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] rauc: bump to version 0.2
Date: Thu, 23 Nov 2017 09:21:52 +0100 [thread overview]
Message-ID: <20171123092152.0f0fac4a@windsurf.lan> (raw)
In-Reply-To: <CAAkeqgVVYW4BZ6tUH20Guxdgz3qay6D4nj+Jz9F5eT6Kn-Ygjg@mail.gmail.com>
Hello,
On Wed, 22 Nov 2017 18:11:12 -0800, Andrey Yurovsky wrote:
> > Isn't that specific to your RAUC use case? I assume other people can
> > use RAUC without using signed squashfs images.
> >
> > So perhaps we shouldn't make host-mksquashfs a mandatory dependency
> > like your patch does?
>
> No, that's just how rauc works, there's no other use case. That is, it
> always make a signed squashfs image (there's no option to make
> unsigned images or any other format). If mksquashfs isn't present, the
> host tool is effectively useless since it can't make bundles, that's
> why I feel that it's a run-time dependency and needs to be selected.
OK, thanks for the explanation! Is this dependency new in 0.2, or it
was already needed for the current 0.1.1 version of RAUC ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-23 8:21 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
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 [this message]
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=20171123092152.0f0fac4a@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