Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: aespipe: add host variant
Date: Tue, 2 Feb 2016 18:43:17 -0300	[thread overview]
Message-ID: <56B122F5.9000002@vanguardiasur.com.ar> (raw)
In-Reply-To: <20160201200235.6cba4eb2@free-electrons.com>

Thomas,

El 01/02/16 a las 16:02, Thomas Petazzoni escribi?:
> Dear Ariel D'Alessandro,
> 
> On Mon,  1 Feb 2016 12:37:27 -0300, Ariel D'Alessandro wrote:
>> Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar>
>> ---
>>  package/Config.in.host         |  1 +
>>  package/aespipe/Config.in.host | 10 ++++++++++
>>  package/aespipe/aespipe.mk     |  1 +
>>  3 files changed, 12 insertions(+)
>>  create mode 100644 package/aespipe/Config.in.host
> 
> Can you give a justification as to why we would want to add aespipe as
> a host package ? We generally try to limit the number of host packages
> we add to package/Config.in.host, so it's good to include a
> justification as to why it is a good idea to include aespipe as a
> menuconfig-selectable host package.

The justification is pretty much what Arnout said:

""
Post-image scripts may want to encrypt the resulting image with aespipe
(and decrypt it in the update tool on the target), so it is useful to
have the host version and to be able to select it in the configuration.
""

In fact, that's exactly why I added host-aespipe to one of my projects.
Is this enough to include it as a host package?

Thanks!

-- 
Ariel D'Alessandro, VanguardiaSur
www.vanguardiasur.com.ar

  reply	other threads:[~2016-02-02 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 15:37 [Buildroot] [PATCH] package: aespipe: add host variant Ariel D'Alessandro
2016-02-01 18:41 ` Arnout Vandecappelle
2016-02-02 21:36   ` Ariel D'Alessandro
2016-02-01 19:02 ` Thomas Petazzoni
2016-02-02 21:43   ` Ariel D'Alessandro [this message]
2016-02-03  8:31     ` 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=56B122F5.9000002@vanguardiasur.com.ar \
    --to=ariel@vanguardiasur.com.ar \
    --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