pure-sh-bible VS Bazel

The guy who wrote it, also wrote a POSIX Shell bible: https://github.com/dylanaraps/pure-sh-bible

Do you have any specific examples to cite? The snippets are meant to be run in POSIX-compliant shells like dash/yash/ash/etc, not just Bash in compatibility mode.

In fact, there used to be a section which listed workarounds[1] for bugs in dash, but they have since been fixed[2]. If you are still using an old version of dash, you may need to use them.

[1] https://github.com/dylanaraps/pure-sh-bible/commit/70f410ebb...

[2] https://github.com/dylanaraps/pure-sh-bible/issues/13

Personally, I would steer clear of a script that installs dependencies on it's own. Us sysadmins prefer to manage our own dependencies, generally speaking. Instead consider a README that outlines how to meet/install dependencies for the script, or try to find ways to write your script in pure Shell or Bash without using tools like awk, jq, etc. Consider having a look at the Pure Sh Bible for examples of how to do many useful things in pure Sh.

POSIX Shell Tutorial POSIX shell cheat sheet GitHub - dylanaraps/pure-sh-bible: 📖 A collection of pure POSIX sh alternatives to external… Shell Scripting Tutorial

There is the "pure bash bible" but it seems less than maintained these days: https://github.com/dylanaraps/pure-sh-bible

Otherwise you're stuck reading the POSIX standard: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V...

Look at this: https://github.com/dylanaraps/pure-sh-bible

Wow, if you curl it, there's a lot of boilerplate code there.

Maybe built using Bazel?

https://bazel.build

Bazel by Google

Luckily a feature to limit the disk cache size is in development: https://github.com/bazelbuild/bazel/issues/5139

This is a problem that Bazel (https://bazel.build) solves in a very convenient way. You can just keep using the paths relative to the repository root, and as long as you properly declare your test needs that file it will access it without problems. Or you can use the runfile libraries to access them too.

When doing research for this lab exercise I looked at both vcpkg and conan. Both are package managers that would automate the installation and configuration of my program with its dependencies. However, when it came to releasing and sharing my program my options were limited. For example, the central public registry for conan packages is conan-center, but these packages are curated and the process is very involved. There was no way conan-center would accept a class project like mine. Alternatively, I could host a conan package on a public Artifactory repository, but accessing the package requires users to add the repository to their conan remote. This already sounded like too many steps to expect regular users to follow - I already haven't setup any conan remotes, there's no way I could expect regular users to know about conan remotes, let alone have conan installed on their system. After discussing with people online and consulting my instructor, I ultimately decided to do a GitHub release. However, in the future I was encouraged to look into using CMake or bazel.

NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇

> None of this solves C's only REAL problem (in my opinion) which is the lack of dependency management.

Bazel solves this really nicely, I know some people have strong opinions on it but I cannot recommend it enough

https://bazel.build/