Hi Jonathan,

Thanks so much for adding this! Real gold!

On 2026/11/11 13:18, Jonathan Dowland wrote:
By coincidence I was discussing Zig packaging (which I have nothing to
do with) on Lobsters with one of the Zig maintainers. They wrote[1]:

As for vendored dependencies, this is a complete list:

  * C language include files from Clang
  * libc include files and implementation files for various targets
  * libc++, libc++abi, libtsan, and libunwind from Clang


This is, if I am not mistaken, exactly what Jesse had already removed, and it is good to know that this is everything. It will bring the whole thing down a lot!

The whole (short) thread may be of interest. He went on to write

Let me ask this question though: what is the purpose of packaging Zig
into Debian? In my opinion, upstream developers prefer to obtain Zig
directly from upstream. I think the purpose of packaging Zig into
Debian is not for Zig users but so that Zig can be used as a
development package to build other Debian packages. In this case, you
don't need any cross-compilation support or any of these vendored
dependencies. They can be completely omitted from the package. This
hamstrings Zig as a compiler tool, so it would be appreciated if it
were made clear to Zig users that this package is not for them. But I
think that is a path worth exploring for Debian, if the goal is to
build other packages.

I will have to give this some thought, and wonder what others think.

Sure, people writing Zig would want the latest version. They're the ones wanting to perhaps cross compile. What I want currently, is to package software written in Zig. So far, so good.

However, I do not think that means we should reduce Zig-in-Debian to just that skeleton. Via bpo we can keep Zig on, or pretty close to the latest releases of Zig. This would probably be advisable anyway, so as not to have to hop across a lot of seeds when packaging for an upcoming release of Debian every so many years.

For the first upload, however, I think a stripped down version would be a great start. And then we could always add the cross-compiling parts later again.

I think that Clang can be linked from the system, since unstable has LLVM-22, so that's good.

To be continued! And thanks, all!

Kind regards,

    Edmund


--
Edmund Lodewijks <[email protected]>
TZ: UTC+2 / GMT+2

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to