Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Di Lieto <nicola.dilieto@gmail.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [RFC PATCH v2] package/uacme: requires TLS support in libcurl
Date: Thu, 14 Jul 2022 10:05:22 +0200	[thread overview]
Message-ID: <Ys/OQuHfT2vyOdnF@einstein.dilieto.eu> (raw)
In-Reply-To: <55f81de26c9b74283245f427bc7dd7ff4db09c06.1657777745.git.baruch@tkos.co.il>

Hello Baruch

On Thu, Jul 14, 2022 at 08:49:05AM +0300, Baruch Siach wrote:
>v2:
>  Add dependency on crypto back end for uacme itself (Nicola Di Lieto)

This should work. It's perhaps not ideal but I can't see any other way 
to work around the circular dependency issue.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-07-14  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  5:49 [Buildroot] [RFC PATCH v2] package/uacme: requires TLS support in libcurl Baruch Siach via buildroot
2022-07-14  8:05 ` Nicola Di Lieto [this message]
2022-07-17  9:07 ` Yann E. MORIN
2022-07-17  9:09   ` Baruch Siach via buildroot
2022-07-17  9:49     ` Yann E. MORIN

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=Ys/OQuHfT2vyOdnF@einstein.dilieto.eu \
    --to=nicola.dilieto@gmail.com \
    --cc=baruch@tkos.co.il \
    --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