Installing something on arch is easy imo. The CLI is simple and well enough documented, and the package build system is easy to use. For comparison with ubuntu:
pacman -S nameis not harder thanapt install name. And try to install something on ubuntu if it’s not in the official package repos.pacman -S app
It should be “yay [wanted program]” instead of “KDE discovery” in my opinion
Paru
Does yay integrate with flatpack and snap?
Why the hell would I want snap?
Yay -S “Am I a joke for you?”
I’ve just been using yay, what does the -S do am I missing something important?
-S, --sync
Synchronize packages. Packages are installed directly from the remote repositories, including all dependencies required to run the packages.
Did pacman get packagekit support or are we just talking about flatpaks here?
Arch Wiki has still this warning
Warning
As explained in a GitHub comment by a Package Maintainer, “Handling system packages via packagekit is just fundamentally incompatible with our high-maintenance rolling release distro, where any update might leave the system in an unbootable or otherwise unusable state if the user does not take care reading pacman’s logs or merging pacnew files before rebooting.”
Wait, I am supposed to care about .pacnew files?
Anyway, so far all I found there is new optional dependencies.
I rather wonder what happens when manual intervention is needed, like when JDK started being in conflict with JRE.Octopi is a decent compromise: https://linuxvox.com/blog/octopi-linux/
Yep
So its less about lack of packagekit support in pacman and more about lack of manual intervention features in GUI software managers?
it is more about arch’s philosy being your system may not boot next update, happens pretty much no where else, except windows, manjaro and sometimes ubuntu
My last Fedora version upgrade was a test of my troubleshooting skills, for sure.
It has been working for a while, but it’s not recommended
Thank you for the clarification
Did pacman get packagekit support
It appears using pacman on Arch is the recommended method for the repos, per this issue adding warnings: https://invent.kde.org/plasma/discover/-/merge_requests/829
or are we just talking about flatpaks here
https://apps.kde.org/discover/ ->
“With Discover, you can manage software from multiple sources, including your operating system’s software repository, Flatpak repos, the Snap store, or even AppImages from store.kde.org.”
So, were talking about flatpaks.
Imagine being so inept that you can’t use a terminal to install a terminal-based update. Arch users are posers and script kiddies and need to STFU
you need to run pacman -S sense-of-humor
Fun hobby you have spreading negativity on lemmy.
I work with computers all day, I don’t want to work when I come home lol.
I get where most comments saying to use pacman or yay but it’s not a good idea to install everything with terminal. Also KDE discover uses flathub and into bazaar is a better client for it.
I’m not an expert, but I thought on Arch you are specifically not supposed to use the discover store because it can cause partial updates which can in turn cause major problems.
However, the point still stands, pacman and the AUR are easy and have nearly everything.
The AUR is a great resource but it’s also being sold as a package repository users don’t need to actively think about or understand. I honestly think malware is going to be much more common on the AUR if we aren’t careful.
I keep hearing this claim online but the Arch bible (which you really should be familiar with if you use Arch) and pretty much everyone that knows anything will tell you that the AUR is useful, but not something to blindly use. I recommend everyone check the
PKGBUILD, verify the source URLs are correct, and check the diffs when updating. It’s not that much effort.And since it comes from a single (user) package repository, you’ll probably have hundreds of people doing the same, or even going a step or two further and looking into the code, reporting the package if anything bad is going on. Still miles better than downloading
.exefiles you find from a Google search, even if you were lazy and didn’t do the aforementioned checks. (But if you don’t do that, you should probably just use Flatpaks or similar.)
Eh. I haven’t had issues for a few months and I back up my files on a weekly basis and -Syu once or twice a month. Worst case scenario, I’ll just reinstall and restore from backup.
Also, I mainly use Discover for high level stuff like browsers and IDEs.
As a Debian slut this level of sweating over updates is wild to me.
Yeah but imagine reading about a new release of something and it appearing in your updates the same day. Shiny new software every day is addicting.
You’re not wrong. That said my broke ass can’t afford cutting edge hardware so most of the time it doesn’t matter.
When it does, I can usually compensate with either a NixOs profile install, a container of some sort (or Flatpak), or just building the emefferr from source.
On the flip side, reading about an exploited vulnerability in a package and then realizing your machine isn’t affected because Debian has an outdated package in it’s repo
You can use it for Flatpaks which works great for a lot of people.
Flatpak just working would be a nice thing. Everytime I try they fuck something new up…
(Last time I thought about installing Steam via Flatpak on Arch to get rid of all the multilib 32bit stuff not needed for aynthing else anymore it worked for nearly 4 days. Then
flatpak updaterandomly uninstalled its nvidia drivers because an “update” removing the old package first, then realizing it can’t find the new one make total sense of course.)If I learned anything with Steam it’s to never install it as a Flatpak.
The original image gives me strong “Shepard, Tali, and Garrus doing shenanigans” vibes.
How did they fuck up so badly that ending? Ahhhhhh
