all: move Zig packages we write/maintain into the main repo about mach HOT 7 CLOSED

TODO list for closing this issue

• Move mach-ecs code into main repo
• Move mach-gamemode code into main repo
• Move mach-sysaudio code into main repo
• Move mach-sysgpu code into main repo
  • Close/merge all pending pull requests first
• Move mach-core code into main repo
  • Close/merge all pending pull requests first
• machengine.org docs updated to reflect new usage
• Ensure website docs have clear usage instructions showing how to just use one of these packages with no extra dependencies compared to before:
  • mach-sysaudio
  • mach-sysgpu
  • mach-core
• mach-core-starter-project is updated
• mach-core migration guide shows how to update
• Repository READMEs are updated to indicate the code has moved
  • mach-ecs
  • mach-gamemode
  • mach-sysaudio
  • mach-sysgpu
  • mach-core
• After we nominate Zig 2024.03 #1147 - ensure dependencies are using lazyDependency where possible

from mach.

All done except for #1175 which will happen after we update Zig.

from mach.

I think that's an option we can explore on a case-by-case basis if download size ever becomes a problem, yep.

from mach.

@Calinou Ah! Thanks, it should be https://github.com/hexops/mach/blob/main/src/gamemode.zig - fixed.

As for the issue tracker, we try to keep all issues in the main repo https://github.com/hexops/mach/issues and just prefix them with e.g. gamemode: and labels to keep it all in one place so nothing is forgotten

appreciate the heads up!

from mach.

One small suggestion regarding package size: you could store all packages in one repo, but still split them into separate tarballs for distribution.
Since the mach docs recommend downloading packages from the website already (as opposed to using github's tarball URLs) it would be easy to host separate tarballs on the website for each project.

However, the downside is that it would still require multiple build.zig.zon entries for people using multiple mach packages, whereas merging them all into one package with multiple modules would only need one entry.

Of course, as you say, there's probably no reason to do this since all the libraries you're proposing to merge are pretty small. I just thought I'd suggest it as an option :)

from mach.

I like this as I found all of mach's segments being broken up into different repos quite confusing and made it not super clear to me how things were supposed to integrate. Having the core features together makes a lot more sense imo

from mach.

The link on the text here in the README of https://github.com/hexops/mach-gamemode seems to be broken. I can't report it there as issues are disabled on that repository.

from mach.