Here how a CLI run looks like doing maak --list in a directory with a maak.scm file:
https://postimg.cc/9wYTHBjQ
Hey all I have an experimental Docker/Podman build here, which you can take for a spin, it works well for me, I don't have any macOS devices to test on yet though, LMK.
Docker tarball hosted on 2 sites: https://limewire.com/d/IHVnx#Pz9q6EwDwL https://filebin.net/gevqik62yzwfxa8u/maak-docker.tar.gz
Once you downloaded this tarball, you can import it with docker load < my.tar.gz
Installing via Guix will always remain more convenient and powerful but docker/podman will work for cross-platform pretty good. Say for example you have a maak file with a task serve, at /home/joe/hacking/hygguile/maak.scm , you could run it as so:
docker container run -v /home/joe:/home/joe localhost/maak:latest maak -f /home/joe/hacking/hygguile/maak.scm serve
Due to popular demand :) Maak is now also available as an experimental Docker container, from DockerHub (also compatible with Podman).
https://hub.docker.com/repository/docker/jjba23/maak/general
You can also build images of maak yourself, using guix pack. See the maak.scm file for more. To load these tarball images, you can do podman load < my.tar.gz
Then you can run Maak from the container, and bind your local filesystem to give access, for example:
docker container run -v /home/joe:/home/joe
docker.io/jjba23/maak:latest maak -f /home/joe/hacking/maak/maak.scm --list
How does this compare to Blue? Blue, to me, seems much more full-featured and ready to be inserted into projects today. Your build system is more-or-less barebones and looks to me more like a plain Makefile in Scheme rather than a full build system, which makes me question how useful it could be in replacing say autotools or meson
A community for the lovers of the scheme programming languages