4 ms·
Have you seen Just? https://github.com/casey/just https://github.com/casey/just It's make-like but supposedly improves on some of the arcane aspects of make (I
by nicoburns 6y ago
Have you seen Just? https://github.com/casey/just https://github.com/casey/just
It's make-like but supposedly improves on some of the arcane aspects of make (I can't judge how successful it is at that as I've never used make in anger).
- skore 6y agoI've seen it before but discarded it because since my workflow is heavily file-based, I DO need makes capacity as a build system, not just a task runner. Will check it out to see whether that changed. edit: Yeah, I can't see how I can make it work for a file-based approach.
- jamwaffles 6y agoWe use it a bit for https://github.com/embedded-graphics/embedded-graphics https://github.com/embedded-graphics/embedded-graphics and I have to say I love it. It's just the right balance between configuration variables/constants and "a folder full of bash scripts". I highly recommend giving Just a try.
- cytzol 6y agoI love Just, but I love it because it's not a build system — I already have a build system, I just need a standard "entry point" to all my projects so each command a user could use to interact with the actual build system is in the same place for each project. I wouldn't build, say, a C project with Just and Just alone, where it tracks the dependencies between files and only rebuilds what's necessary. So while it's replaced one use of Make for me, I can't rightly call it a Make replacement.
- nicoburns 6y agoWould you build a C project with make? One might argue that C could do with a better build system like other languages have. I don't use C much, but I hear that these exist.
- candied_scarf 6y agoi wont use this because the author sucks up all justfiles files with no way for a user to opt out and isnt fully clear on this. use it on some private or company thing that accidentally goes public, oops he has your file now in his repo. if it was opt-in to him monitoring i might be more open. maybe i should fork and change the filename to keep this from happening
- audience_mem 6y agoWhat are you talking about? Where does he "suck up" all Justfiles?
- candied_scarf 6y agohttps://github.com/casey/just#janus https://github.com/casey/just#janus they end up here https://github.com/casey/janus/tree/master/fetch https://github.com/casey/janus/tree/master/fetch
- audience_mem 6y agoI see. Interesting.
- bluejekyll 6y agoOne of the reasons I know I still rely on Make instead of Just, is about how available make is, and pretty much any tool (be it a new implementation of make in Rust or Just) will have to deal with the fact that make is already a default on so many systems. That makes make a great entry point for any project. Does anyone have a general suggestion about how to work around this? The goal being, sync a project and not need to install anything to get going. One thing I do sometimes is to use make as the entry point, and it has an init target to install the necessary tools to get going (depends on who I know to be the target audience).
- andoriyu 6y agoyeah, until you meet the system with different make, and now you have to install GNU/Make.
- berkes 6y agoThis sounds like what I do: Makefile with distinct steps: install, build, test, lint, deploy. Those steps call underlying tools, depending on the platform, framework, language. E.g. in one project it will install rbenv, bundle, npm, yarn etc. Call Rake, npx, that odd docker wrapper, etc. Or deploy with git in one project and through capistrano or ansible in another. As a dev, in daily mode, all you need is 'make lint && make test && make deploy'. All the underlying tools and their intricacies are only needed when it fails or when you want to change stuff.
- bluejekyll 6y agoYeah. Exactly. I do this when I think there will be users who don’t already have all the dev tools installed, and I don’t want them to have to download and install everything.