Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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.
DISCLAIMER: Arch Linux is not a beginner friendly distribution, and this is not a recommendation or good practice.
I know how to use pacman -S. I have yet to experience a Discover related issue after months of use.
yay chrome, enter, 1, enter
much easier than discover
why do people get intimidated by installing an arch package?
i recently wanted to play morrowind and i use the terminal like a search engine for programs. i just typed "yay openmw" and voila it was there, checked in the aur if the package is clean and installed it by clicking enter 3 times.
and i thout "yay ^_^ that was easy! :3", got off a ship in seyda neen and killed fargoth with my bare fists as soon as i locked eyes with him.
Stand up, there you go. You were dreaming. What's your name?
why do people assume I get intimidated by installing an arch package?
Pacman -Syu java
Windows users : π¨π¨π°
sudo pacman -S (name), far easier than any gui in my opinion.
Pamac is great too, and it can run all your updates at shutdown.
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
Octopi is a pretty great GUI software manager
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.
Oh yeah, I added a disclaimer.
It should be βyay [wanted program]β instead of βKDE discoveryβ in my opinion
Paru
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.
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."
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.