All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] openssl: always build apps
Date: Thu, 2 Jul 2015 22:54:56 +0200	[thread overview]
Message-ID: <5595A520.6090903@mind.be> (raw)
In-Reply-To: <20150702120402.4e4e3b9d@free-electrons.com>

On 07/02/15 12:04, Thomas Petazzoni wrote:
> Dear Beno?t Th?baudeau,
> 
> On Thu, 2 Jul 2015 11:58:01 +0200, Beno?t Th?baudeau wrote:
> 
>> Yes. My intent was to keep the rules minimal, but I agree that it is better as
>> you suggest. I will send a v2.
> 
> Great, thanks.
> 
>> I have a question about the management of the scripts depending on Perl, though.
>> Doing as you suggest hides this behavior in the .mk, so the users won't know
>> that they have a choice just by looking at the configuration. Do you think that
>> it does not really matter, or that a comment or a depends on / select should be
>> added to the Config.in?
> 
> We generally try to not clutter menuconfig with too many
> comments/options: we can't make visible in menuconfig every little
> possible dependency. That's why we use a lot of "automatic optional
> dependencies": a package automatically uses another package if it is
> available, without having this dependency visible from a
> menuconfig/Config.in point of view.

 We (or at least, I) do like to have such a thing mentioned in the help text,
however. The help text does not clutter the menus so there is no reason to be
terse there.


 Regards,
 Arnout

> 
> I think it's a bit the same here. If you know you need that specific
> Perl script from OpenSSL, then we assume that you are smart enough to
> realize that you might need to enable a Perl interpreter for your
> target.
> 
> Yes: we do believe our users are smart! :-)
> 
> Thanks,
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-07-02 20:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 10:54 [Buildroot] [PATCH 1/2] openssl: support building the binary without MMU Benoît Thébaudeau
2015-06-19 10:54 ` [Buildroot] [PATCH 2/2] openssl: always build apps Benoît Thébaudeau
2015-07-01  9:14   ` Thomas Petazzoni
2015-07-02  9:58     ` Benoît Thébaudeau
2015-07-02 10:04       ` Thomas Petazzoni
2015-07-02 20:54         ` Arnout Vandecappelle [this message]
2015-07-02 21:22           ` Thomas Petazzoni
2015-07-02 21:38             ` Arnout Vandecappelle
2015-07-03  7:32               ` Thomas Petazzoni
2015-06-21  4:45 ` [Buildroot] [PATCH 1/2] openssl: support building the binary without MMU Thomas Petazzoni
2015-06-21 12:34   ` Arnout Vandecappelle
2015-06-21 14:07     ` Benoît Thébaudeau
2015-06-30 14:44     ` Thomas Petazzoni
2015-06-30 14:44 ` 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=5595A520.6090903@mind.be \
    --to=arnout@mind.be \
    --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.