On Fri, Mar 07, 2025 at 12:49:59PM +0000, Daniel P. Berrangé wrote: > 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.
That's fine for me. Should we go with qapi-go or go-qapi or ? Cheers, Victor
signature.asc
Description: PGP signature
