also, why would any dependency of your projects at work be implicit? all dependencies should be captured somehow, the very least in some documentation.
at our company, we use shell.nix files to declare all of our dependencies, so everyone has the exact same software available on their development workstations.
it's not a completely trivial thing to do, but worth investing into it, to lower the chance of surprises, which will happen when you can afford them the least...
here is an example to get started:
``` with import (builtins.fetchTarball { name = "nixos-unstable-on-2021-05-16"; url = "https://releases.nixos.org/nixos/unstable/nixos-21.05pre2893... sha256 = "1kilrk0ipvldf4rrn6aq6v2bj2jfhbz33cjb9w9ngqmbmr2f94wd"; }) { };
let project-jdk = jdk11; clojure = callPackage ./deps/clojure { jdk11 = project-jdk; };
in mkShell rec { buildInputs = [ coreutils cacert direnv nixfmt curl jwt-cli fd python3 nodejs (yarn.override { nodejs = nodejs; }) project-jdk clojure yaml2json
modd
devd
overmind
];
shellHook = ''
export LC_CTYPE="UTF-8" # so tar and rlwrap won't complain
'';
}
```it shows how u would use your custom package (for clojure in our case) and how would u pin there state of the whole package repository to a specific point in time.
in the past I've used es, the extensible shell (https://wryun.github.io/es-shell/), this way, without bothering my colleagues with teaching them about it. they just git pull, press enter in a shell within the hour repo and direnv will pull down any new dependencies.