All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] Move the libssh setup from configure to meson.build
Date: Fri, 10 Dec 2021 14:05:17 +0100	[thread overview]
Message-ID: <9e55f8f5-1588-367d-3681-54c77d77700f@redhat.com> (raw)
In-Reply-To: <20211209152230.GL1127@redhat.com>

On 12/9/21 16:22, Richard W.M. Jones wrote:
> On Thu, Dec 09, 2021 at 04:08:24PM +0100, Thomas Huth wrote:
>> On 09/12/2021 15.55, Richard W.M. Jones wrote:
>>> On Thu, Dec 09, 2021 at 03:48:01PM +0100, Thomas Huth wrote:
>>>> It's easier to do this in meson.build now.
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>>  v2: Added the missing "config_host_data.set('CONFIG_LIBSSH', libssh.found())"
>>>>
>>>>  configure                     | 27 ---------------------------
>>>>  meson.build                   | 13 +++++++++----
>>>>  meson_options.txt             |  2 ++
>>>>  scripts/meson-buildoptions.sh |  3 +++
>>>>  4 files changed, 14 insertions(+), 31 deletions(-)

>>> I should say that my interest in the ssh driver in qemu is not that
>>> much these days.  I've been telling people to use nbdkit-ssh-plugin
>>> instead.  It's more featureful and running it in a separate process is
>>> probably safer too.
>>
>> Then it's maybe time to deprecate the ssh driver in QEMU?
> 
> Weeeellllll ...  I didn't necessarily want to say that.  Others may be
> using it, and deprecating working software causes trouble for some.
> But I'll let others have their say on this.

The deprecation process is slow, users have 8 months to notice it,
and we might discover contributors willing to maintain it. IOW more
PROs than CONs IMHO.

> I will mention that RHEL 9.1 will replace qemu's curl and ssh drivers
> with nbdkit-curl-plugin and nbdkit-ssh-plugin.  For RHEL users this
> should happen transparently.  Libvirt will substitute an external
> nbdkit process when it sees the appropriate <disk> in the XML (all
> RHEL users are required to use libvirt instead of qemu directly).  Of
> course qemu doesn't need to care about what RHEL does, this is just
> for your information.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2016527
> 
> Rich.
> 



  reply	other threads:[~2021-12-10 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 14:48 [PATCH v2] Move the libssh setup from configure to meson.build Thomas Huth
2021-12-09 14:55 ` Richard W.M. Jones
2021-12-09 15:08   ` Thomas Huth
2021-12-09 15:22     ` Richard W.M. Jones
2021-12-10 13:05       ` Philippe Mathieu-Daudé [this message]
2021-12-13  7:15         ` Thomas Huth
2021-12-15  7:56 ` Petr Vorel

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=9e55f8f5-1588-367d-3681-54c77d77700f@redhat.com \
    --to=philmd@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=thuth@redhat.com \
    /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.