It should be βyay [wanted program]β instead of βKDE discoveryβ in my opinion
this post was submitted on 25 Feb 2026
468 points (96.4% liked)
linuxmemes
30644 readers
1313 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
Paru
Does yay integrate with flatpack and snap?
Why the hell would I want snap?
AUR pkgbuild files are basically just bash scripts. You can integrate them with anything.
No, but then flatpak and snap fail most of the time anyway.
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 name is not harder than apt install name. And try to install something on ubuntu if it's not in the official package repos.
ubuntu: pacman -S name is not harder than apt install name.
Eh, it's a teensy bit harder, since you have to remember what -S means, rather than the easy to remember and plain English 'install'. But, yeah, not much of a difference.
And try to install something on ubuntu if itβs not in the official package repos.
1: Go to that something's website.
2: look for their download/install instructions page, scroll to Linux instructions if necessary.
3: Install instructions for Debian/Ubuntu are usually the first one listed, and typically just consist of a few commands you can copy and paste over without modifying.
It isn't particularly difficult in most cases.
4: those commands were written for previous version of Ubuntu and now dependency tree doesn't compute, also one of the commands is to add their custom repo, and you don't have keys for it so it doesn't work anyway. You try to remove the bad repo and now your apt is all fucked. You regenerate your repo list, googled the package and your version name, random stackexchage page gave you their live repo, but it needs a newer version of a library that incompatible with 54 of something that you already have. You learn about snap, installed 43Gb of something, it exists but still doesn't really work because package maintaiers didn't actually move it to snap, it was someone else. By this point you copy-pasted so many commands into your terminal you afraid it gained sentience. You call your more computer literate friend, he starts saying something about incompatible dependancies, containers, and you don't really understand much. By the end, you decide that you didn't actually want the software.
Later you discover that your sound doesn't work anymore, and there is an error when you reboot.
Good ending: you installed Arch, installed yay and instead of remembering unmemorable -S you just do yay package_name and you're very happy with your choices.
load more comments
(1 replies)
load more comments
(2 replies)
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."
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 is more about archβs philosy being your system may not boot next update
Yeah ... no thanks. I'll be okay with slightly outdated versions of various packages, as long as they still work.
I mean I've been running an arch derivative for nearly ten years and the last time I got got was an Nvidia driver bug in 2020.
As much as arch talks about it it doesn't happen that often.
I'm not sure it's ever happened to me. I imagine it must have, because of Arch's reputation, but I can't recall it ever actually happening to me personally.
Octopi is a decent compromise: https://linuxvox.com/blog/octopi-linux/
load more comments
(1 replies)
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.
Not right away, but they will eventually cause issues if you let them sit as pacnew. I use meld to resolve the conflicts and merge the two.
meld makes the task less annoying +1
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.
IME, KDE Discover and similar app stores are so unreliable, telling beginners to use them is akin to harmful misinformation
If you need a GUI software manager, my suggestion is to not use arch
Hard agree. I always struggled when using Discover, as a Beginner. Don't know if I could make it work now as a more experienced user, Because I don't use it and don't have a need to. Learning how to use 'pacman -S $pkg_name' was super simple and is very fast. Sure I don't have a nice GUI, that lets me browse what apps are there to be installed, but I have a webbrowser for that.
load more comments
(6 replies)
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 .exe files 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.)
All official resources, Arch maintainers and high quality guides have been putting a ton of effort into teaching people how to use the AUR safely. That hasn't stopped some people, even back before Arch got really popular, but you can't reach everyone. Alternative package managers and pacman wrappers made the AUR a lot more accessible, which isn't necessarily a bad thing, but there are good reasons for all the caution. Combine that with Arch increasing in popularity and getting picked up by all the shitty influencers and you get a lot of people ,who don't know what they're doing, installing everything from the AUR with their CLI/GUI of choice. Then you've got Arch derivatives making AUR packages easily accessible from the start, bad advice on places like reddit etc.
Long story short: it seems that over the years whenever I check in, users that barely know how it works are happily installing random shit from random people on the AUR because they saw it in a YT video or something.
load more comments
(2 replies)
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.
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
load more comments
(1 replies)
load more comments
(5 replies)
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.
Technically correct answer but not super helpful imo.
yay <package name> starts a search from which you enter your selection(s) from matches. yay -S <package name> installs the package directly, errors if it's not found
The original image gives me strong "Shepard, Tali, and Garrus doing shenanigans" vibes.
load more comments
(1 replies)
Pacman -Syu java
Windows users : π¨π¨π°
Pamac is great too, and it can run all your updates at shutdown.
sudo pacman -S (name), far easier than any gui in my opinion.
view more: next βΊ