On Tue, 2026-11-17 at 21:55 +0200, Edmund Lodewijks wrote:
> Hi Ivan,
> 
> On 2026/11/17 21:03, Ivan Carvalho wrote:
> > > Maytham wants version numbers, which I agree with. Ivan suggests also
> > > renaming the package to zig-core, because... I don't know the reason
> > > why?
> > 
> > This was suggested in debian-devel because functionalities are being
> > stripped. Upstream is very worried about people running "apt install
> > zig" and having a suboptimal experience.
> 
> There is no precedence that I could find in the archive for doing this 
> kind of renaming, but I am happy to be corrected. I did but a cursory 
> search.
> 
> What is missing in terms of functionality, that I can see:
>   - cross-compilation
>   - static musl-linking (I intend to ITP the musl headers if Zig makes it
>     into the achive)
>   - glibc version pinning. This is because of missing abilists and
>     start.S. I think we can get this back in, it's free code after all.
>   - ThreadSanitiser (libsan). I haven't really looked into this yet.
> 
> So yeah, Zig is not fulfilling its promises of building static libraries 
> that run everywhere.

zig-0.17-minimal / -core / other name does make a lot of sense though,
considering these missing features.

You could put this under zig-0.17, but then you would be pressured to
make that have every feature working, and it does not make very
obviously clear to consumers that it is missing parts unless they read
the description.

[...]
> (2) At first, we ONLY upload the package 'zig-0.17', which installs 
> zig-0.17 and zig-0.17-src.
> 
> Now, when you install zig (apt install zig), you get an error, because 
> that package does not exist. If someone really wants to install zig, 
> they have to type apt install zig-0.17 (which meant they went looking 
> for it to find it), and the Description will say clearly that there is 
> no glibc in that version, and what that costs.
> 
> At the same time, ghostty can be built against zig=0.17 (it requires 
> 0.17 anyway). We will possibly end up with a couple of versions of Zig 
> in the archive, as long as it's not backwards compatible?

Yes, we probably will.

[...]
> > > What do you think? Does this make sense?
> > 
> > Please send an MR to https://salsa.debian.org/zig-team/book with your
> > package layout proposal. We need to show the community that we are
> > organized to be taken seriously.
> 
> Will do. Funny reasoning, though.
> 
> > I don't object to numbering the package, but while you highlighted
> > cases of package numbering remember that we are closer to
> > https://tracker.debian.org/pkg/nim and
> > https://tracker.debian.org/pkg/swiftlang of being a niche programming
> > language.
> 
> I suggest that we follow mostly what Go does, except for that they don't 
> follow DEP-14 as much, presumably because Go predates it ;-) We can 
> start with a clean bill, and laying the best foundations prevents 
> changes later. I'll lay something out in the Book tomorrow, I hope, but 
> Golang + DEP-14 is where I took my inspiration.

Single zig git repo with branches for the different versions e.g.
debian/0.17, debian/0.17-minimal etc? If this is what you mean, then I
agree.

--
Maytham
> 

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to