this post was submitted on 04 Feb 2026
13 points (93.3% liked)

Linux

12287 readers
705 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
13
Supac - a declarative package manager for Linux, scriptable in nushell (codeberg.org)
submitted 1 week ago by innocentz3r0@programming.dev to c/linux@programming.dev
2 comments fedilink hide all child comments
 

cross-posted from: https://programming.dev/post/45148310

Supac - a declarative package manager written in Rust, scriptable in nushell

Supac is a declarative package manager written in Rust fully scriptable in nushell. It's meant to make it easy to use the native package managers in existing distros without going through the associated headaches of using Nix, while maintaining the ergonomics of structured data in nushell.

Currently supported backends are:

  • Archlinux and derivatives
  • flatpak
  • cargo/cargo-binstall
  • uvx (packages only for now)
  • rustup toolchains

I daily drive it, and it works well. Feel free to give it a try!

top 2 comments
sorted by: hot top controversial new old
[โ€“] HappyFrog@lemmy.blahaj.zone 2 points 1 week ago* (last edited 1 week ago) (1 children)

Now this looks interesting. I personally use chezmoi and scripts to install and manage the apps that I want. Having a dedicated manager would be ideal.

Edit: it says that disabling backends is currently not supported, does that mean that it doesn't worn in environments without pacman for example?

[โ€“] innocentz3r0@programming.dev 2 points 1 week ago

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.