TVL depot development (mail to depot@tvl.su)
 help / color / mirror / code / Atom feed
From: Ali Abrar <ali.abrar@obsidian•systems>
To: "depot@tvl.su" <depot@tvl.su>
Subject: Improvements to buildGo
Date: Tue, 14 Oct 2025 01:17:13 +0000	[thread overview]
Message-ID: <DS0PR14MB70947FCE35989D1DB98858BB9FEBA@DS0PR14MB7094.namprd14.prod.outlook.com> (raw)

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

Hi there,

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.

-embedcfg file
      Read go:embed configuration from file.
      This is required if any //go:embed directives are used.
      The file is a JSON file mapping patterns to lists of filenames
      and filenames to full path names.

I have added support for this on my fork and would be happy to contribute it.

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.

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.

Thanks,
Ali


Ali Abrar

Partner, Obsidian Systems



(888) 611-7759 x102



ali.abrar@obsidian•systems

https://obsidian.systems



[-- Attachment #2: Type: text/html, Size: 7338 bytes --]

                 reply	other threads:[~2025-10-14  1:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DS0PR14MB70947FCE35989D1DB98858BB9FEBA@DS0PR14MB7094.namprd14.prod.outlook.com \
    --to=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).