Damus
elsat · 26w
@ nostr:npub1chakany8dcz93clv4xgcudcvhnfhdyqutprq2yh72daydevv8zasmuhf02
jack (n/acc) · 26w
Appimages flatpaks nix and dnf
GHOST · 26w
sudo apt install
jack (n/acc) · 26w
Angry turk’s opinion https://image.nostr.build/a25394920fa9fbf08515ea2f4897584e3a7e0238516fdaa883c817e95b439298.jpg
Islamic Audiobooks Central · 26w
Flatpak and Flathub have solved the app distribution issue on most distros. People can fight it or come up with something better which I doubt is happening in the near future... maybe Kaiming if Chinese companies invest in it.
Kieran · 26w
Install from source, apt, sometimes snap
DeveRoSt · 26w
Snappy (snap packages), yes it is canonical yes the store is not really open but technically the best solution (from point of security). And it ships possibly to all important Linux Distros.
Awiteb · 26w
I just use nixpkgs, all the packages are hash-verified. Cool
Matt - Not Your Entropy, Not Your Coins · 26w
I typically go with whatever the app maker recommends. RPM is common. Flatpaks are common. AppImage is less common. Sometimes you get a tarball but that is way less common than it used to be. Flathub (as a flatpak source) has gotten a lot better, but I like to make sure a Dev is the one who actually...
Bill Cypher · 26w
More people should set up repos and get added to extrepo instead of publishing a .deb and expecting us to dpkg -i
⚡tephen · 25w
I learned reprepro and had my own repo (apt get) for a few years. Woowee was upgrading things annoying. Until I got into automation with bash! I mostly build from source, or sometime grab binaries from git if they build for my architecture.