Shelly is another option, comes pre installed on CachyOS. It's aiming to modernise pacman. It's been pretty good for my usage.
It has a GUI that can handle native repos, the AUR, flatpaks and app images. It can also be used in your CLI as well
Shelly is another option, comes pre installed on CachyOS. It's aiming to modernise pacman. It's been pretty good for my usage.
It has a GUI that can handle native repos, the AUR, flatpaks and app images. It can also be used in your CLI as well
Yay. Add ssu (a 120 loc C tool) as "sudobin" in it's config and you've got a passwordless package manager.
And btw, that question is covered already.
Im running arch proper, nothing come pre-installed. But I originally used paru and then installed yay cuz I was troubleshooting something. Never removed it.
Fo what it’s worth, it doesn’t hurt anything to have multiple installed so you can see which you like. They shouldn’t interfere with eachother.
Paru, so Pacman & AUR...
With exactly one exception: Steam via flatpak because that's the single package left that would need 32bit libraries from multilib-repo since Wine finally left those dependencies behind.
i used their version of discover (forgot the name) and found it has mostly everything i was looking for (surprisingly so)
You can choose between things like flatpak or aur packages, but you're gonna have to use pacman either way, since your core packages are still managed by pacman even if you decide to install most things through flatpak. Just wanted to point that out in case you were thinking of not using it at all anymore, cause it's definitely not good to have your system get extremely out of date overtime. Having said that, it's a matter of preference. The aur has more packages available, but flatpak has verified packages available, so assuming you stick to those, it could be safer. It also offers things like sandboxing. When i was on arch i only used the aur. I usually go with whatever has the most packages available or whatever is most convenient.
Your question is not Arch specific, it's "should I use flatpaks?" And the answer in my opinion is probably no.
Flatpaks are a good idea to isolate certain applications and to provide a uniform way of installing packages. So there might be some apps that are not available in your native package manager, but do provide flatpaks. For those cases flatpaks are probably preferred. But Arch based distros have the AUR, so there are a lot of apps that aren't packaged for Arch that you can still get as a native package. Sure, using the AUR is risky and if you're not on actual Arch things might break sporadically because of mismatched dependencies (although I think CachyOS is full parity of packages with Arch, so that's maybe more of a Manjaro warning).
But flatpaks are clunky, bloated, require annoying permissions to be set to do basic things, and require you to update two package managers to do a full system update. They are more appealing for systems where you don't want to give users root access but still allow them to install programs, but for your own computer I have never seen the appeal.
I guess you could put it that way. For most general applications, I prefer to use flatpak over pacman. Pacman and arch's repos to me are still very confusing over other package managers (dnf, apt, etc)
I use yay, as it comes by default with EndeavourOS. It's basically an AUR helper that uses pacman and works quite the same.
Flatpak is a different package manager and has nothing to do with your system packages. They are not exclusive, I use both. So what you basically asking isn't which package manager people use, but rather which package format.
Same here, I tried a number of arch derivatives and arch as well when I got a new desktop last year (after many years of mac work computers, iMac desktop for my kids, mostly Alpine images in the cloud/on k8s, and many many years of mostly Debian and fedora derivatives before I had kids and had time to putter around with *nix). Endeavor suited my needs (some local LLM stuff, personal browsing, a few OSS projects, and Steam) and yay has generally worked great to bridge the gap between pacman and aur.
Personally, I use pacman when possible and flatpak when it's not. I try to avoid the aur as I have had too many problems with missing dependencies or version conflicts. Plus, I don't generally need things that are not in the repositories so it rarely comes up.
"But flatpaks are not lean!" While this is true, I find flatpaks don't break my system. Flatpaks do use more resources, from storage to RAM, but I have plenty of both so it's not really a concern.
Pacman plus the AUR is the move on Arch based distros. The AUR gives you access to basically everything, and paru or yay handles the build chain without pain. Flatpak has its place for apps that ship messy runtime dependencies, but for most things it adds an unnecessary isolation layer. Have you tried paru as your AUR helper yet?
I sometimes prefer Flatpak over AUR, because I do not trust everyone on the AUR to run scripts with root rights on my system. At least Flatpaks are a bit sandboxed (even if the sandbox is an illusion) and the programs don't install and run with root rights. Sometimes the Flatpak is from the original developer and the script in AUR is not. Or the AUR script is not updated well and often enough, unlike day one Flatpak updates. But Flatpaks do not integrate well in your system and applications can look out of place too. There is a lot to consider, besides what you already mentioned.
I use both, prefer the AUR in optimal cases.
I don't like Flatpak, so that makes it an easy choice for me. Flatpak apps never quite integrate properly
I like having Flatpaks as a fallback option, but if something is available in the arch repos, aur or chaotic-aur, I'll always go there first
Always use native pkgs if possibile (so use pacman/paru)
Look into the Chaotic AUR. It offers pre compiled AUR programs. Almost every app I really need has been there. If it's not in there and I really need it and will get used often I'll get it from the AUR.
I dont really like flatpaks much. I'll use it if it's easy and I dont plan on using the app much. Apps like Bottles. They are nice to have but rarely do I use it.
What do you mean by "bloated"? How many more bytes does the flatpak version have compared to its counterpart?
Depends on the program, they don't use system libraries so if they have a lot of dependencies then they'll be larger.
An example:
Steam Flatpak: 35MB
Steam pacman: 19MB
On one hand, it's only a few MB. On the other hand, it's 54% larger.
Flatpaks can also depend on other flatpaks. For example, graphics card support requires about 1-1.5GB of flatpak dependencies even though your system already has graphics card drivers.
I just don't understand how people still use Flatpak.
Once I had to download a small app 400kB more or less, and suddenly it started downloading 200MB of environment packages.
Never again.
I just reinstalled arch last weekend and have both paru and yay installed. Only real difference between them is yay is Go and paru is Rust. Both work great and very similarly. I think the paru dev originally worked on yay.
I tend to choose the pacman and aur over flatpaks or snaps, something about the isolation layer never sat right with me.
Why do you have both paru AND yay installed at the same time? As someone who likes Rust, I maybe should have switched to paru too. But I just can't justify the change, because yay comes preinstalled and works just fine, and paru seems to not offer anything worthwhile the change.
If you install yay, it gives you pacman + AUR wiþout sudo. To be pedantic, þere is a sudo happening, but it's hidden. In any case, you don't ever type "sudo" and it is one command. I expect oþer yay-like tools are similar.
Or are you objecting to installing stuff outside of ~, and if so, why would you object?
Why are your "th"s turning into that weird b?
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0