From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Victor Toso <victortoso@redhat.com>
Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"John Snow" <jsnow@redhat.com>,
"Andrea Bolognani" <abologna@redhat.com>
Subject: Re: New git repository for Go bindings
Date: Fri, 7 Mar 2025 12:49:59 +0000 [thread overview]
Message-ID: <Z8rrd8DoLUVh_Je1@redhat.com> (raw)
In-Reply-To: <xu3qsijvpbguwdnlj6ovomlkd2wggd76x2lvfusmczljhnmx4f@kgw6di2754ta>
On Fri, Mar 07, 2025 at 01:30:38PM +0100, Victor Toso wrote:
> Hi,
>
> I've been working on and off in having Go bindings for QEMU's
> QAPI specification. The last version [0] seems to be accepted so
> far but we would like not to have that in qemu.git.
>
> In the past [1], Daniel suggested creating a repo per each
> generated schema: go-qemu.git, go-qga.git, go-qsd.git
>
> While that works well from the point of view of Go applications
> and is neat organized too, afaict they are all bounded to QEMU's
> release schedule so it might be enough to create a single repo
> such as:
>
> qapi-generators.git
> └── golang
> ├── module.py # The go generator
> ├── qemu # For qapi/qapi-schema.json
> │ ├── doc.go
> │ ├── gen_iface_command.go
> │ ├── gen_iface_event.go
> │ ├── gen_type_alternate.go
> │ ├── gen_type_command.go
> │ ├── gen_type_enum.go
> │ ├── gen_type_event.go
> │ ├── gen_type_struct.go
> │ ├── gen_type_union.go
> │ ├── go.mod
> │ ├── protocol.go
> │ └── utils.go
> ├── qga # qga/qapi-schema.json
> └── qsd # storage-daemon/qapi/qapi-schema.json
>
> Or perhaps a per language repo?
I'd suggest we keep the repo dedicated just for 'go' language, as mixed
language repos are more trouble than they are worth when it comes to
dealing with language specific build tools.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-03-07 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 12:30 New git repository for Go bindings Victor Toso
2025-03-07 12:49 ` Daniel P. Berrangé [this message]
2025-03-07 13:51 ` Victor Toso
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=Z8rrd8DoLUVh_Je1@redhat.com \
--to=berrange@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=victortoso@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.