11–20 of 25 posts
We need a Bash package manager and global repo now! (If you had told me in 2001 that Javascript would have had NPM and bash not, I would not have believed you.)
[2] https://cppget.org/?packages=bash
[3] https://build2.org/build2/doc/build2-build-system-manual.xht...
Yes, I know the readme is not up to date with recent changes/improvements.
We need a Bash package manager and global repo now! (If you had told me in 2001 that Javascript would have had NPM and bash not, I would not have believed you.)
If you can afford using a package manager then you can afford using something more sophisticated than bash. The whole point of bash is that it’s ubiquitous: be it an air-gapped embedded system, a recovery image or a full desktop environment, you can count on it having either bash or something reasonably close, no strings attached. Introducing a Rube Goldberg package manager would go against this.
Bash isn’t necessarily gonna be installed on a bsd system and it’s not exactly recent on macOS - it’s possible it’ll be dropped there too.
I’m not saying don’t write shell, I’m saying don’t assume bash specifically is available.
There’s only one bash, but there’s plenty of shells that implement POSIX “sh”.
We need a Bash package manager and global repo now! (If you had told me in 2001 that Javascript would have had NPM and bash not, I would not have believed you.)
Looking at how e.g. some official AWS code is written and distributed in shell (like ec2-instance-connect-config), that's not too far I guess from how even big orgs handle Bash code.
We need a Bash package manager and global repo now! (If you had told me in 2001 that Javascript would have had NPM and bash not, I would not have believed you.)
We need a Bash package manager and global repo now! (If you had told me in 2001 that Javascript would have had NPM and bash not, I would not have believed you.)
At my company, for what we deploy as Bash, we take care to write it according to regular software engineering standards (code + tests + doc), build OS-specific packages, distribute them using proper repos (rpm, deb) and bake them into vm machine images/containers where needed. We declare dependencies between packages to specify (versioned) dependencies between different code libraries. Works for us. Looking at how e.…
Shameless plug but I was not a huge fan of working with bash as I liked python, so I made Sultan: https://sultan.readthedocs.io/en/latest/
Shameless plug but I was not a huge fan of working with bash as I liked python, so I made Sultan: https://sultan.readthedocs.io/en/latest/