Right now, you can do it in two ways:

• Don’t have the Arch key at all. supac will silently skip it.
• You can write a small wrapper in package.nu that checks the presence of your preferred arch package manager in $env.PATH, if it’s there then it’ll insert the key and value, and not otherwise.

I’d mostly go with 1 unless you’re sharing your non-arch config with an arch config on two separate machines.

Dcli looks interesting! The long term goal of supac is to support many different relevant package managers as backends, so that all sorts of packages and language toolchains can be managed. Besides, nushell being a scripting AND shell language massively helps with that.

From what I understand (I’ve never used mise), mise is meant for programming environments and tools. Supac works with your distribution’s package manager to manage all your system packages and also language toolchains like rustup and uvx (uvx backend doesn’t manage toolchains yet, it’s being developed though).

What it doesn’t manage are programming environments, basically, you cannot use it to spawn something like a nix devshell. Hope it makes sense. This is more meant to be along the lines of something like nix, but friendlier and easier.

deleted by creator