All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Greg Kurz" <groug@kaod.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [RFC] Move tools sources to the tools directory (was Re: [PATCH v2] MAINTAINERS: Fix the location of tools manuals)
Date: Thu, 4 Feb 2021 15:57:19 +0100	[thread overview]
Message-ID: <20210204145719.GJ6496@merkur.fritz.box> (raw)
In-Reply-To: <20210204144700.GN549438@redhat.com>

Am 04.02.2021 um 15:47 hat Daniel P. Berrangé geschrieben:
> On Thu, Feb 04, 2021 at 03:40:06PM +0100, Kevin Wolf wrote:
> > Am 04.02.2021 um 15:31 hat Peter Maydell geschrieben:
> > > On Thu, 4 Feb 2021 at 14:23, Wainer dos Santos Moschetta
> > > <wainersm@redhat.com> wrote:
> > > > Unrelated too, but allow me to ask:
> > > >
> > > > Should we move the tools (qemu-img, qemu-io, qemu-nbd...etc) to the
> > > > tools directory (virtiofsd seems to feel alone there)?
> > > 
> > > I think that would be a good thing, yes (things documented in docs/tools
> > > should have their source code in tools).
> > 
> > Maybe we should define then what a tool is. I think contrib/ has a few
> > more things that could be considered tools.
> 
> The distinction of contrib/ vs tools/ is supposed to be more a
> reflection on the quality of the program.
> 
> contrib/ should be considered demo-ware, no back compat guaranteed,
> may or may not work, no testing guaranteed, no man pages.
> 
> tools/ should be for any program that we intend end users to actively
> use in real world, with an expectation of quality and stable CLI and
> man pages.

Maybe the difference should be related to what we build by default then?
Just checking what executables my build directory contains, I guess
these are candidates for tools/:

qemu-bridge-helper
qemu-edid
qemu-img
qemu-io
qemu-keymap
qemu-nbd
qemu-pr-helper

Almost all of them are currently in the root directory today. Only
qemu-pr-helper is in scsi/.

And then there is qemu-storage-daemon which lives in storage-daemon/
today and whose executable ends up in a storage-daemon/ subdirectory of
the build directory since the Meson conversion, which is inconsistent
with all other tools.

I haven't checked other subdirectories for more executables that might
exist.

Kevin



  parent reply	other threads:[~2021-02-04 14:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 13:54 [PATCH v2] MAINTAINERS: Fix the location of tools manuals Wainer dos Santos Moschetta
2021-02-04 13:59 ` Philippe Mathieu-Daudé
2021-02-04 14:22   ` [RFC] Move tools sources to the tools directory (was Re: [PATCH v2] MAINTAINERS: Fix the location of tools manuals) Wainer dos Santos Moschetta
2021-02-04 14:31     ` Peter Maydell
2021-02-04 14:40       ` Kevin Wolf
2021-02-04 14:47         ` Daniel P. Berrangé
2021-02-04 14:50           ` Peter Maydell
2021-02-04 15:02             ` Paolo Bonzini
2021-02-04 15:06               ` Daniel P. Berrangé
2021-02-04 17:37                 ` Philippe Mathieu-Daudé
2021-02-04 17:39                   ` Paolo Bonzini
2021-02-04 15:04             ` Daniel P. Berrangé
2021-02-04 14:57           ` Kevin Wolf [this message]
2021-02-04 14:47         ` Peter Maydell
2021-02-04 14:40     ` Paolo Bonzini
2021-02-04 17:42       ` Philippe Mathieu-Daudé
2021-02-04 17:55         ` Paolo Bonzini
2021-02-04 18:24     ` Eric Blake
2021-02-04 20:57     ` John Snow
2021-03-09 17:41   ` [PATCH v2] MAINTAINERS: Fix the location of tools manuals Wainer dos Santos Moschetta
2021-03-09 19:48     ` Thomas Huth
2021-03-09 20:44       ` Laurent Vivier
2021-03-09 22:54       ` Greg Kurz

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=20210204145719.GJ6496@merkur.fritz.box \
    --to=kwolf@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wainersm@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.