From: sterni <sternenseemann@systemli•org>
To: Ali Abrar <ali.abrar@obsidian•systems>, "depot@tvl.su" <depot@tvl.su>
Subject: Re: Improvements to buildGo
Date: Sat, 29 Nov 2025 17:42:49 +0100 [thread overview]
Message-ID: <c87ccef0-8bd6-4ace-a774-3aae1051025e@systemli.org> (raw)
In-Reply-To: <DS0PR14MB70947FCE35989D1DB98858BB9FEBA@DS0PR14MB7094.namprd14.prod.outlook.com>
On 10/14/25 03:17, Ali Abrar wrote:
> I'm using buildGo and I have some patches that I'd like to submit
> upstream. The first, and most important, is adding support for embed
> configuration.
embed and cgo support are the obvious missing pieces for buildGo, so
you're welcome to submit your changes for review. Either via Gerrit (see
<https://code.tvl.fyi/about/docs/REVIEWS.md>) or via mail if that's more
convenient for you.
> I also have added a good number of go packages under third_party/gopkgs,
> but I'm not sure if you actually want that to become a big library of
> packages or if they are better placed elsewhere.
Given that we have no good way to (semi-)automatically update third
party go packages in depot at the moment, I'd vote against accumulating
packages which are not depended on in depot itself.
> Last, I'm wondering if you had any thoughts on spinning up development
> environments for go packages that are packaged with buildGo. If you've
> already got something in this vein that works, I'd love to borrow your
> ideas. Otherwise, I'd be happy to share what I come up with.
Nothing I'm aware of. In general, buildGo has mostly been in maintenance
mode as of late. Almost every Go release manages to break buildGo in
some way via often undocumented changes in the behavior of the CLI, so
further developing has been feeling like a risk given that anything we
built is almost certain to randomly break at some point (usually it is
fixable after some head scratching, but that's anything but guaranteed).
~sterni
prev parent reply other threads:[~2025-11-29 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 1:17 Ali Abrar
2025-11-29 16:42 ` sterni [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=c87ccef0-8bd6-4ace-a774-3aae1051025e@systemli.org \
--to=sternenseemann@systemli$(echo .)org \
--cc=ali.abrar@obsidian$(echo .)systems \
--cc=depot@tvl.su \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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://code.tvl.fyi
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 read-only IMAP folder(s) and NNTP newsgroup(s).