From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] package/libssh2: Add selectable crypto libraries
Date: Sun, 5 Nov 2017 14:31:45 +0100 [thread overview]
Message-ID: <20171105133145.GJ2996@scaer> (raw)
In-Reply-To: <6626fb96-a677-2bbe-d801-7352cc4c6428@mind.be>
Arnout, All,
On 2017-11-05 13:46 +0100, Arnout Vandecappelle spake thusly:
> On 05-11-17 11:40, Peter Korsgaard wrote:
> >>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> > >> > This does affect people updating Buildroot, so it needs to be mentioned in CHANGES.
> > >>
> > >> Why don't we just keep the old logic instead? E.G. leave the select
> > >> openssl if !(mbedtls || libgcrypt) and then change the selects to
> > >> depends on in the choice:
> > >>
> > >> choice
> > >>
> > >> config BR2_PACKAGE_LIBSSH2_MBEDTLS
> > >> bool "mbedtls"
> > >> depends on BR2_PACKAGE_MBEDTLS
> > >>
> > >> ...
> > >>
> > >> Doesn't that give us the best of both worlds? Same behaviour as before
> > >> by default and still the option to explicitly chose when multiple
> > >> backends are available?
> >
> > > That's what Sam did in the initial iterations of his patchset, but
> > > Arnout and Thomas (IIRC) both requested he replaces that with a select
> > > instead.
> >
> > Hmm, I could only find Arnouts mail asking to use select, but he didn't
> > write why. Arnout, why not use depends on here?
>
> I was just applying the default principle that you should use select rather
> than depends unless there is a good reason to use depends. I hadn't thought of
> backward compatibility back then, and I didn't think of using depends now.
>
> I've already committed, can you fix it up?
I think that using select is better, so we should keep it as-is, even
though that means backward incompatibility.
After all, a user should review their configuration pon updating
Buildroot.
Note: this exposes a flaw in the way we handle legacy: it can only take
care of options that were removed, and can not account for new options
like this case. There is nothing we can do about this, though... :-/
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-11-05 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 16:22 [Buildroot] [PATCH v4 1/1] package/libssh2: Add selectable crypto libraries Sam Voss
2017-11-04 21:58 ` Arnout Vandecappelle
2017-11-05 8:01 ` Peter Korsgaard
2017-11-05 8:19 ` Yann E. MORIN
2017-11-05 10:40 ` Peter Korsgaard
2017-11-05 12:46 ` Arnout Vandecappelle
2017-11-05 13:31 ` Yann E. MORIN [this message]
2017-11-05 13:50 ` Peter Korsgaard
2017-11-05 13:50 ` Peter Korsgaard
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=20171105133145.GJ2996@scaer \
--to=yann.morin.1998@free.fr \
--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.