You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of [Flox](https://flox.dev] to create immutable, audited builds, I want to be able to simply install the CALM CLI into my build environment like other dependencies using "flox install calm".
Potential Solutions:
This will require creating a package and registering it with the Flox catalogue (this may actually mean creating it as a Nix package - not investigated yet). Whilst we're at it, we can create an environment config for developing CALM itself and add to our git repo. This would give the added benefit or a new developer being able to simply "flox activate" to get all the dev env dependencies rather than having to install (and manage) individually.
The text was updated successfully, but these errors were encountered:
I haven't come across Flox before. Can I ask what you're looking to use CALM for and whether this is something you would be able to contribute to help understand where this would sit in priorities?
I'm also curious about Flox vs. all the different repositories for these kind of tools.
Mac has brew, ubuntu has apt, windows has choco, etc.
Once CALM is in Flox, can anyone install it - or is it only usable by people in a Nix-like environment e.g. NixOS? I know Nix can be quite a heavy and opinionated environment to set up, so curious to hear your thoughts.
It is usable by anyone who has installed Flox - currently this means any Linux flavour plus MacOS. This would mean CALM being packaged as a Nix package, but I'm not exactly sure what's involved in that.
Feature Request
Description of Problem:
As a user of [Flox](https://flox.dev] to create immutable, audited builds, I want to be able to simply install the CALM CLI into my build environment like other dependencies using "flox install calm".
Potential Solutions:
This will require creating a package and registering it with the Flox catalogue (this may actually mean creating it as a Nix package - not investigated yet). Whilst we're at it, we can create an environment config for developing CALM itself and add to our git repo. This would give the added benefit or a new developer being able to simply "flox activate" to get all the dev env dependencies rather than having to install (and manage) individually.
The text was updated successfully, but these errors were encountered: