qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Richard W.M. Jones" <rjones@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: Mon, 13 Dec 2021 08:15:02 +0100	[thread overview]
Message-ID: <6eb8cf35-21dc-9275-fa9f-dabcfd2d99e5@redhat.com> (raw)
In-Reply-To: <9e55f8f5-1588-367d-3681-54c77d77700f@redhat.com>

On 10/12/2021 14.05, Philippe Mathieu-Daudé wrote:
> 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.

Right - one of the ideas of the deprecation process is that this is a way to 
find out if a feature is still used in practice, and whether someone still 
cares about it being maintained. So if you think that there is a better 
alternative these days and don't want to maintain the feature forever 
anymore, just send a patch to docs/about/deprecated.rst to mark it as 
deprecated there (and the status in MAINTAINERS should maybe rather be "Odd 
Fixes" than "Supported", I guess?).

  Thomas



  reply	other threads:[~2021-12-13  7:16 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é
2021-12-13  7:15         ` Thomas Huth [this message]
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=6eb8cf35-21dc-9275-fa9f-dabcfd2d99e5@redhat.com \
    --to=thuth@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).