Yep, it should cover you alright! I use all the 5 package managers mentioned here (hence the order :p). Scriptability and post hooks in particular make it even better (cloning/copying dots, activating systemd units, other stuff, etc).
Haha, fair enough. The reason I even created this in the first place was because of how painful nix/nixOS is to use in general. Nushell is far simpler, and much more ergonomic to deal with. Especially with how much it supports structured data.
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.
Right now, you can do it in two ways:
I'd mostly go with 1 unless you're sharing your non-arch config with an arch config on two separate machines.