Re: [NEW] textproc/go-chroma

On Sat, 11 Jul 2026 11:36:48 +0200, Igor Zornik <mocheryl@mocheryl.org> wrote: > Attached is the version without the playground. Unfortunately it still > needs a custom distributable due to the project using Go submodules, > but at least now it's "make dist"-able because it doesn't require any > non-OpenBSD utilities. > > The port now also additionally sets "commit" and "date" variables. I'm > not sure if this is frowned upon, because I haven't seen any other > (Go) port do this, but you can just remove it if it's too much. There's at least another go port that does it: sysutils/kopia I wouldn't hardcode the values. Is the commit id really helpful since there's the version? I think the real build date is better, like kopia does. > Happy testing the new version! This version builds here :) Cheers, Daniel

Re: lang/node, wip v8-wasm support for yarn berry

On 7/10/26 10:43 AM, Fabien Romano wrote: [...] > There are a bunch of node tests failing that may be worthwhile checking. > fs.watch / watch-mode : > parallel/test-fs-promises-watch* > parallel/test-fs-watch* > parallel/test-watch* > sequential/test-watch-mode* I'll reply separately to your other points. From what I can tell by manual testing fs.watch, it works to the same degree as sysutils/inotify-tools does, given sufficiently high values for kern.maxfiles and openfiles, but not exactly as on Linux - for which the tests appear to have been designed.