On 2026/03/28 18:06, Volker Schlecht wrote:
> zig moved from GH to Codeberg on November 25, 2025 - I propose to update the
> port to fetch the source from the new repo. The tag 0.15.2 coincides with the
> hash from ZIG_COMMIT, so I think we can just use the tag?
> 
> What do you think?

> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/lang/zig/Makefile,v
> diff -u -p -r1.30 Makefile
> --- Makefile	24 Oct 2025 18:49:56 -0000	1.30
> +++ Makefile	28 Mar 2026 17:01:42 -0000
> @@ -5,13 +5,11 @@ BROKEN-powerpc64 =	ld: error: undefined 
>  
>  COMMENT =	zig compiler and toolchain
>  
> -DISTNAME =	zig-0.15.2
> +V =		0.15.2
> +DIST_TUPLE =	codeberg ziglang zig ${V} .
> +REVISION =	0
>  
> -GH_ACCOUNT =	ziglang
> -GH_PROJECT =	zig
> -GH_COMMIT =	${ZIG_COMMIT}
> -
> -# see https://github.com/ziglang/zig/tree/0.15.x
> +# see https://codeberg.org/ziglang/zig/src/branch/0.15.x
>  ZIG_VERSION =	0.15.2

it doesn't seem useful to have ZIG_VERSION and V as separate vars?

>  ZIG_COMMIT =	e4cbd752c8c05f131051f8c873cff7823177d7d3
>  
> @@ -36,6 +34,8 @@ MODCLANG_LANGS =	c c++
>  MODCLANG_VERSION =	20
>  
>  SEPARATE_BUILD =	Yes
> +
> +WRKDIST =	${WRKDIR}/zig

this one is so annoying, it seems like it should be simple to fix
so that dist-tuple.port.mk sets it correctly, but nothing I try works...
(all the ports using codeberg DIST_TUPLE explicitly set WRKDIST to what
you get from ${WRKDIR}/${_project})