Rewrite build system in Literally Anything Other Than Bash

[clo4]

Rewrite build system in Literally Anything Other Than Bash

[clo4]

Definitely Python. It has everything I need build into its standard library, and the file watcher should be done externally, eg. using entr, watch, etc. Having to set up a virtual environment is a hard no, so all file watching packages are out of the picture. While I could use Deno for its better dependency management, the complexity of JS/TS isn't worth it for this.

[clo4]

More thinking. There shouldn't be one major build script, instead each project should have its own that can support its own features, and there can be a sort of orchestration script that executes all of them in parallel in the root directory.

[clo4]

So here's my current idea. There will be an executable file in each datapack's directory called build.fish, using fish for its sane shell scripting syntax. This is the logic responsible for zipping the contents and creating the datapack. Each build script will create a zip file called datapack.zip in the current directory. As part of the Nix flake builder, it will then rename this datapack according to the name and version specified.

Using the builder should look something like this:

{ buildDataPack }:
buildDataPack {
  pname = "afk";
  version = "1.2";
  minMinecraftVersion = "1.13.x";
  maxMinecraftVersion = "1.21.0";
  src = ./.;
}

And the build script might look like this:

set files LICENSE pack.png pack.mcmeta data

rm -rf build
mkdir -p build
cp -R $files build
cd build

# Older version compatibility
for dir in **/function
  cp $dir {$dir}s
end

zip -r ../datapack.zip $files

obviously there could be more complicated logic there, but that's a starting point and for most should be all that's necessary.

[clo4]

... and that's basically what I did. New build system landed in 4ef8015, except it doesn't use a build script, the compat logic is handled by the preBuild phase in each default.nix. This is also where the minimum and maximum minecraft versions that it supports are defined. The build phase is just zipping the contents of the zip list, and the install phase is moving it to the correct location with the correct name. The output contents will be the same as they would have been with the old build script.