Hi! Thanks for looking into it. As for the comments:
> Any reason to name the port go-chroma instead of just chroma? There's already a chroma port. It's mentioned in the Makefile. I'm open for accepting a better solution to resolve naming conflicts. > Is the -web subpackage really useful? Well, no. As I've already written in my opening post, it seems it serves mostly for demonstrative purposes and it looks nice so I've added it anyway as an option. That's my personal take on it. I can modify DESCR based on further decisions. > Anyway is there an issue with tgz? It doesn't seem to build here: Sorry to hear that. I don't know what could've gone wrong. It looks OK to me. I've prepared another .tgz with the port updated to 2.27 as that was released in the meantime. 'make install-all' works on today's amd64 snap. I've also replaced tab with a space in WANTLIB. Hopefully you'll have better experience with this version. On Tue, 2026-07-07 at 12:53 -0400, Daniel Jakots wrote: > On Tue, 16 Jun 2026 21:14:43 +0200, Igor Zornik > <[email protected]> > wrote: > > > Hello, ports! > > > > Attached is a new port that is used for colorizing many languages > > into > > various output types. The main part of the port is the gochroma > > binary. It takes an input and performs some syntax highlighting on > > it. You can use it, for example, in cgit to make your code display > > on > > the web page more colorful. The project also comes with a web site, > > but I don’t see much practical use for it beside looking nice so I > > just separated it into a subpackage to avoid installing a whole > > bunch > > of unnecessary stuff. I think it’s mostly used for demonstrative > > purposes. > > > > Any feedback is welcome. Package info below. > > > > Comment: > > general purpose syntax highlighter in pure Go > > > > Description: > > Chroma takes source code and other structured text and converts it > > into syntax highlighted HTML, ANSI-coloured text, etc. > > > > Chroma is based heavily on Pygments, and includes translators for > > Pygments lexers and styles. > > > > Maintainer: Igor Zornik <[email protected]> > > > > WWW: https://github.com/alecthomas/chroma > > Any reason to name the port go-chroma instead of just chroma? > > I think both DESCR could be a bit specific than just to have the last > line change. Is the -web subpackage really useful? > > The WANTLIB line shouldn't have a tab since it comes from the output > of > the tool that doesn't include a tab. > > Anyway is there an issue with tgz? It doesn't seem to build here: > /usr/ports/textproc/go-chroma$ make patch > ===> Building from scratch chroma-2.26.1 > ===> go-chroma-2.26.1 depends on: esbuild-* -> esbuild-0.28.1 > ===> go-chroma-2.26.1 depends on: go-=1.26.4p0 -> go-1.26.4p0 > ===> Verifying specs: c pthread c pthread > ===> found c.103.0 pthread.28.1 > ===> Checking files for chroma-2.26.1 > /bin/sh: syntax error: `(' unexpected > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3322 > '/usr/ports/distfiles/chroma-2.26.1.tar.gz': @lock=chroma- > 2.26.1.tar.gz.dist...) > *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2594 > '_internal-fetch': @cd /usr/ports/textproc/go-chroma && > PKGPATH=textproc/go-...) > *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2814 > '/usr/ports/pobj/chroma-2.26.1/.extract_done': @cd > /usr/ports/textproc/go-ch...) > *** Error 2 in /usr/ports/textproc/go-chroma > (/usr/ports/infrastructure/mk/bsd.port.mk:2722 'patch': @lock=chroma- > 2.26.1; export _LOCKS_HEL...) >
go-chroma.tgz
Description: application/compressed-tar
