patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Cole Helbling <cole.e.helbling@outlook.com>
Cc: devel@spectrum-os.org, Puck Meerburg <puck@puckipedia.com>
Subject: Re: [PATCH platform2 0/2] Make vm_protos compatible with protoc-gen-go 1.5.x
Date: Wed, 30 Jun 2021 09:12:23 +0000	[thread overview]
Message-ID: <20210630091223.p6tnych3z27utcpi@eve.qyliss.net> (raw)
In-Reply-To: <SJ0PR03MB5581E8B67454489E5810F73BB3039@SJ0PR03MB5581.namprd03.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]

On Mon, Jun 28, 2021 at 01:35:51PM -0700, Cole Helbling wrote:
> On Mon Jun 28, 2021 at 10:31 AM PDT, Alyssa Ross wrote:
> > My previous attempt[1] at this was totally wrong, because I didn't
> > understand what change needed to be made, and didn't have any way of
> > testing it.
> >
> > To make sure this time that I got it right, I wrote a package for
> > tremplin[2], which was the only Chromium OS component I could find
> > that was written in Go and actually used vm_protos.  With these
> > changes, I was able to add "${vm_protos}/lib/gopath" to tremplin's
> > extraSrcPaths, and get a successful build.
> >
> > [1]: https://spectrum-os.org/lists/archives/spectrum-devel/20210627165035.899276-1-hi@alyssa.is/
> > [2]: https://chromium.googlesource.com/chromiumos/platform/tremplin
> >
> > Alyssa Ross (2):
> >   common-mk: add goproto_library source_relative opt
> >   vm_tools: proto: set go_package correctly
> >
> >  common-mk/proto_library.gni   | 7 +++++++
> >  vm_tools/proto/BUILD.gn       | 5 +++++
> >  vm_tools/proto/tremplin.proto | 2 +-
> >  vm_tools/proto/vm_crash.proto | 2 +-
> >  vm_tools/proto/vm_guest.proto | 1 +
> >  vm_tools/proto/vm_host.proto  | 1 +
> >  6 files changed, 16 insertions(+), 2 deletions(-)
> >
> > --
> > 2.31.1

Hey Cole, glad you're still around. :)

> Good thing I didn't (have enough time to) review that previous patch :P
>
> Is this something unique to this project, or should / will this be upstreamed
> (if it isn't already)?

It's probably not that useful to upstream, because they're still using the
old version of protoc-gen-go, and when they do get around to upgrading,
I imagine they'll want to do it across the board, so it'll end up being
different to the fix I've made here that only affects one component.
I expect they'd want to just set source_relative unconditionally, for
example, whereas I've made it an option that defaults to off.  I did it
that way because I don't have the resources to check all of Chromium OS,
when the only bits of it I know how to build are the bits I've packaged
for Spectrum.

Additionally, I'm a bit wary about upstreaming things to Google, because
they have a mandatory CLA.  If we had some big change where we'd really
benefit from them maintaining it upstream, I might be able to overcome
my reservations, but this isn't it.

> That aside, diff LGTM.
>
> Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>

Thanks!  I'll be sending some patches shortly that add these patches to
chromiumOSPackages.vm_protos in Spectrum's Nixpkgs.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-06-30  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 17:31 [PATCH platform2 0/2] Make vm_protos compatible with protoc-gen-go 1.5.x Alyssa Ross
2021-06-28 17:31 ` [PATCH platform2 1/2] common-mk: add goproto_library source_relative opt Alyssa Ross
2021-06-28 17:31 ` [PATCH platform2 2/2] vm_tools: proto: set go_package correctly Alyssa Ross
2021-06-28 20:35 ` [PATCH platform2 0/2] Make vm_protos compatible with protoc-gen-go 1.5.x Cole Helbling
2021-06-30  9:12   ` Alyssa Ross [this message]

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=20210630091223.p6tnych3z27utcpi@eve.qyliss.net \
    --to=hi@alyssa.is \
    --cc=cole.e.helbling@outlook.com \
    --cc=devel@spectrum-os.org \
    --cc=puck@puckipedia.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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).