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.
I had issues with btrfs-assistant. It's a permissions thing, tho. Might work if I added myself as an administrator, but I like the security of needing sudo, so pacman version it is.
yay chrome, enter, 1, enter
much easier than discover
That's not easier, maybe quicker though.
its easier once you know how, but i see what youre saying
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?
AUR pkgbuild files are basically just bash scripts. You can integrate them with anything.
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.
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.
Thanks! I initially thought about writing this in my comment in parentheses, but then didn't do because it would've made the comment longer, and I'm not sure if other people want to read the pedantic truth anyways. I'm glad you filled this void.
The instructions for installing on ubuntu only work because of ubuntu's popularity. Also if you can copy-paste commands, you can also just follow build instructions. In arch, these commands are in the PKGBUILD, you don't have to copy them manually. Plus you have the knowledge that you'll have something that you can also deinstall later. Applications' websites usually don't have uninstallation instructions.
Iβm not sure if other people want to read the pedantic truth anyways. Iβm glad you filled this void.
Glad my pedantry could be of service, lol!
The instructions for installing on ubuntu only work because of ubuntuβs popularity.
True, but this is still a very real effect with real-world benefits.
(And I wouldn't necessarily say it's just Ubuntu's popularity. More like, due to Debian and Debian derivatives' popularity, of which Ubuntu is one. Since there are so many popular distros out there that are Debian-based where Debian-style install instructions will work (and quite a few people running Debian itself), it makes sense to give Debian-style install instructions first.)
Also if you can copy-paste commands, you can also just follow build instructions.
In my experience, not so much.
Because even if you follow the instructions exactly, you'll always run into some problem due to your build environment not being quite identical to the developer's build environment, some library being half a version number off, and then cmake fails with a cryptic error message. So then you downgrade that library to the older version and try again, and this time it fails with a different cryptic error message that you can't make any sense of at all this time, or the compiler quits because it says the code is formatted improperly on line 1437 and now you're left wondering whether it's an issue with your compiler or whether you should go in and edit the source code yourself to try and fix that supposed formatting error...
I don't know... I've tried this approach a few times -- usually as a desperate last resort -- and it never seems to actually work. In theory, it should. In practice ... good fucking luck.
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.
Always read the PKGBUILD before running makepkg!
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.
Octopi is a decent compromise: https://linuxvox.com/blog/octopi-linux/
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.
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.
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
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.
Pamac is great too, and it can run all your updates at shutdown.
Pacman -Syu java
Windows users : π¨π¨π°
sudo pacman -S (name), far easier than any gui in my opinion.