Reusable Justfile
yea my PRs cleans up a lot of unused stuff in the Justfile. Having shared maintenance for reusable Justfiles would be good. However in terms of the template, it'd also be good just to keep that very simple.
8 Replies
I added a hhd-dev/rechunk action
and a rootful_unload_action
Strong agree on this.
Bluefin's justfile is right now frozen on the initial implementation.
Main has improvements but definitely still can be updated.
I guess the challenge is how to cleanly abstract everything.
unfortunately Bluerora <=> Bazzite build aren't compatible and Bluefin's is essential infrastructure. We can add more local build stuff at the bottom and make the CI stuff more untouchable. But ideally the image-template could use Bluefin's Justfile
Yeah. There is also something to be said about the Justfile having everything necessary for the recipe instead of composing them together.
Bazzite's Justfile is unused right now
I keep making cool stuff like imagectl rpm-ostree rechunk action or a libvirt runner. Maybe we could make a library with a giant dumpfile
Or sherman has the rechunk on the justfile in bos, no reason that it shouldn't be advertised somewhere. Some images require rechunking to run, and people won't want to setup CI just to do that
Yeah. That was the point of the Justfile rewrite. Make the local build be the same as the CI job
Also every time someone forks our image template they are stuck with that Justfile. So if it was a submodule it could update... but only a minority of people would know how to use it
Maybe we can make a Just action to update the Justfile from image-template lol
Well... I think having a collection of useful recipes is nice. But ultimately it's a task runner. If your build is more complicated than what our thing supports out of the box.... Well you're kinda on your own.
We're not making a bluebuild cli tool