public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Michael Roth" <michael.roth@amd.com>,
	"Konstantin Kostiuk" <kkostiuk@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Eric Blake" <eblake@redhat.com>
Subject: Re: Cleaning up contrib/ and tools/
Date: Tue, 24 Mar 2026 11:44:37 -0700	[thread overview]
Message-ID: <39b64118-7faa-4308-a603-d568cc78de47@linaro.org> (raw)
In-Reply-To: <CAFEAcA-kk29mjGWLrAGjd9AiAW64v0TvWdedZypSH0i43WgQzw@mail.gmail.com>

On 3/24/26 11:33 AM, Peter Maydell wrote:
> On Tue, 24 Mar 2026 at 18:28, Pierrick Bouvier
> <pierrick.bouvier@linaro.org> wrote:
>>
>> On 3/24/26 10:09 AM, Peter Maydell wrote:
>>> And for contrib/, easy ones first:
>>>    * contrib/vhost-user-{blk,bridge,gpu,input,scsi} move to tools/
>>>    * contrib/elf2dmp moves to tools/
>>>    * contrib/ivshmem-client and contrib/ivshmem-server move to tools/
>>>    * contrib/plugins moves to plugins/plugins (or a different subdir
>>>      name of your choice)
>>>
>>
>> I would suggest plugins/contrib or plugins/community, to make clear they
>> are the community contributed ones.
>> @Alex, do you have a different suggestion/preference?
> 
> I firmly do not want us to have anything that claims to be
> "contrib" or "community" or similar. Everything in QEMU is
> community contributed in some sense. Either we care about
> and maintain these plugins, in which case call them "plugins",
> or we do not in fact care about and maintain them, in which
> case delete them. "In the tree but not maintained" is not
> a category I think we should have, and that is what "contrib"
> generally implies.
>

We make sure they build, and test them (manually) on changes. The only 
difference with tests/tcg/plugins is that those are used for make 
check-tcg. I personnally consider both of them as properly maintained.

>> Moving those sources will break build folder hierarchy also, which is an
>> issue for all existing binaries built from contrib anyway.
>> I'm not sure there is anything sane to do to fix that except accepting
>> the breaking change.
> 
> What are we breaking here ? Nothing outside QEMU ought to be
> depending on the layout of our source tree. When we move things
> around we'll update the meson.build and the documentation.
> I don't think we have 'contrib' in our installed-locations
> layout (tools get installed into the bin/ dir, for instance),
> but I might have missed something.
>

I was thinking more about users that might have custom scripts using 
various contrib plugins, or using vhost-* binaries or ivshmem-server or 
elf2dmp. They will be relocated because meson automatically uses layout 
of sources in build folder.
It's not a big deal anyway.

> -- PMM

Regards,
Pierrick


  reply	other threads:[~2026-03-24 18:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 17:09 Cleaning up contrib/ and tools/ Peter Maydell
2026-03-24 17:31 ` Daniel P. Berrangé
2026-03-24 18:28 ` Pierrick Bouvier
2026-03-24 18:33   ` Peter Maydell
2026-03-24 18:44     ` Pierrick Bouvier [this message]
2026-03-25  9:21       ` Daniel P. Berrangé
2026-03-25 10:05         ` Marc-André Lureau
2026-03-25 11:11       ` Alex Bennée
2026-03-25 15:17         ` Pierrick Bouvier
2026-03-25 16:43           ` Peter Maydell
2026-03-25  7:42 ` Kostiantyn Kostiuk
2026-03-25 11:43 ` Markus Armbruster
2026-03-25 14:32   ` Alex Bennée
2026-03-25 16:49   ` Peter Maydell
2026-03-25 16:54     ` Daniel P. Berrangé
2026-03-25 19:41     ` Peter Maydell

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=39b64118-7faa-4308-a603-d568cc78de47@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@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