reproducible-central
bob
| reproducible-central | bob | |
|---|---|---|
| 1 | 33 | |
| 89 | 434 | |
| - | 0.9% | |
| 9.9 | 4.5 | |
| 3 days ago | 10 days ago | |
| Shell | Go | |
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
reproducible-central
-
Is My Package Reproducible Yet?
It's pretty doable to create reproducible builds with gradle or maven: https://reproducible-builds.org/docs/jvm/
Also, releases on maven central typically include a sources.jar along with the binaries. It's required to provide that as well as javadoc to publish on maven central, I think. They also require jars to be signed and there are some manual checks before they activate your account to verify e.g. domain ownership and metadata of your project. It's not perfect but it's better than what many other packagemanagers do. It's actually a bit of a PITA to setup; I've wasted quite a bit of time getting some stuff published there just trying to figure out their convoluted processes and tools and error messages. This stuff is way too hard in it's current form.
Not all projects that use these build tools are fully reproducible but that is probably pretty easy to fix if people raise awareness of issues around this topic.
There's even a website that tracks reproducibility for some common libraries on maven central: https://github.com/jvm-repo-rebuild/reproducible-central#rea...
If you want to use artififacts produced straight from git hashes, tags, or branches, jitpack.io is pretty neat.
bob
- Bob 0.8.0: Keeping Hot Reloading for React, Vuejs or Svelte Functional
- Blob
- FLiP Stack Weekly for 06 February 2023
-
Managing multiple Go versions in the local environment
I use https://bob.build to switch between go versions in my build graph. It's like... ... build: cmd: go build dependencies: [go_1_18]
-
Is My Package Reproducible Yet?
Using Nix[0] should solve the reproducibility of a package. We use its package manager for bob[1] to achieve reproducible builds for projects.
[0] https://nixos.org/guides/how-nix-works.html
[1] https://bob.build/
- Show HN: Reproducible builds using Nix-shell with bob
- Bob 0.6.3 released - An opinionated Bazel competitor which keeps IDE integration and hot-reloading functional by writing build outputs directly to the scope of a monorepo.
What are some alternatives?
devbox - Instant, easy, and predictable development environments
Bazel - a fast, scalable, multi-language and extensible build system
nix-portable - Nix - Static, Permissionless, Installation-free, Pre-configured
nix - Nix, the purely functional package manager
envd - 🏕️ Reproducible development environment
resholve - a shell resolver? :) (find and resolve shell script dependencies)
g - Simple go version manager, gluten-free
nix-ld - Run unpatched dynamic binaries on NixOS
nickel - Better configuration for less
bazel-c-rust-x86_linux-armv7_
Yoopta-Editor - Notion-like editor with similar behaviour
yaml-sucks - YAML sucks.