seph

I suspect this is stale.

This was fixed upstream, and I haven't seen this occur in ages. So I'm going to close this PR.

I haven't seen this happen in a few years. So I'm guessing something got fixed.

I don't think we're going to dig deep here

While we might redo some protocol and interfaces, I don't think we're going to go in this direction

This is super stale, and I don't think we're going to do this

I'm pretty sure this is because of how the update works -- windows starts launcher, which then finds the correct binary, execs it, and _that_ new one starts the service....

While true, this issue is clutter

This is mostly long term research. I'm closing this issue, since it's not an active project. Parts of it survive in PRs

This shouldn't be a change in `pkg/make` it should be a `go generate` somewhere.