hmmm, this never happen to me…
It was a long time ago. 
2 Likes
Like @Aragorn , I too remember it reappearing, which of course I re-removed it.
I do keep the cli version, but rarely use it.
I don’t use snaps or flatpaks, and I don’t care much for the pamac gui,:so I continue to use Octopi - and I like that it seems like more information is readily available than with Pamac where one needs to do more clicking.
3 Likes
In my case, I uninstalled pamac and octopi a long time ago and manage packages with a custom bash script with fzf that uses pacman, yay and flatpak.
I can run this script both in a graphical environment and in console mode. The only difference is that in console mode instead of using the F1 - F10 keys, I use Alt+1 - Alt+9 and Esc, and instead of glyphs I use ascii codes.
1 Like
flatpak came in handy when I couldn’t install gdm-settings due to dependency ‘glib2-devel’
This thread is discussing pamac-cli, not pamac-gui.
Oh i missed that somehow… thanks.
pacman is the de-facto package manager for repository packages on any Arch-based distribution
pamac-cli is developed by Manjaro and has similar features, but is not a duplicate (Identical copy)
pamac has additional options for AUR packages e.g. build and update --aur
command syntax is intended to be similar to package managers on other Linux distributions
pamac will ask for escalated rights if needed, so sudo should not be used
Manjaro also has a GUI package manager (pamac-gtk or pamac-gtk3).
Users can install libpamac-flatpack-plugin or libpamac-snap-plugin to enable Flatpak or Snap package options in the Pamac GUI
KDE Users can also use octopi GUI and yay from Manjaro repositories and continue hating on Manjaro-developed packages
not necessarily hate, maybe just preference for me since the time when manjaro was developing (?) octopi (>10 years ago?) and ported as a qt gui package manager
pamac resemble Discover to me but it may has appeal, easy of use and other features needed to many users
De Gustibus…
I just got in the habit of using yay from Arch. I like it when the command parameters are nearly identical. And I never use yay to update everything. Especially when snapshots are taken automatically for updates.
sudo pacman -Syu
yay -Syu
Then two snapshots.
1 Like
“continue hating on” is a response to users who have previously stated their antipathy to pamac
and do not seem to respect other user’s preferences
1 Like
I don’t hate Manjaro-developed packages, but you have to admit that pamac has lots of bugs, and as a Plasma user, I try to minimize the amount of gtk-based stuff for consistency in look & feel.
If anything, the gtk developers — who are actually the same people as who develop GNOME — are quite known for being resentful, authoritarian and abrasive. Just ask Linus Torvalds — he has clashed with them on more than one occasion.
3 Likes
To be frank, until reading this thread I had the idea in my head, that pamac is just a wrapper for pacman with added functionality just like yay or paru.
Interesting to know, that pamac does not build upon pacman.
I still use pamac, but the gtk base and therefore not fitting theme is frustrating. It’s more like a update notification for me now, as for real system updates I use yay now, and to browse individual packages I use pacseek.
I removed all flatpack’s from my system though and never had any snap’s to begin with.
Better not do that. Use pacman first, and only afterwards use yay.
3 Likes
I want to see a good intend in giving advice, but without any justification or reasoning why it would matter, that advice is pointless to me.
No need to explain everything, but at least some pointers would be welcome.
I’ve seen various instances where pacman commands saved the day after an upgrade was messed up.
In my view, pacman is still needed. It just works better for updates.
I do use pamac GUI, but only as a standalone package manager AFTER I do my system upgrades with pacman.
At that point, I check on AUR upgrades, do package searches (eg for orphans) which get displayed in a nice graphical display and from which I can check dependencies, do installation/removal of individual packages, etc.
So as a tool for one-off package management, it’s helpful.
The problems mainly seem to arise when users think that the pamac GUI is an appropriate tool for system upgrades, and that upgrades are a simple one-click exercise.
@Ganimede
The concern is in doing an upgrade of both system and AUR packages at the same time. Very often, packages get pushed from main repos to AUR because the package became deprecated and no longer needed by the original package it was a dependency of. These packages should be removed by the user, not updated.
But if you simply do an all-in-one upgrade of everything marked upgradeable in system and AUR, you may be updating things you do not need at all.
I recall some time in the past when python2 was deprecated and pushed to AUR, but users who upgraded everything in one go had no idea and the rebuild of python2 tied up their system for a long time.
For most people, python2 would have been no longer needed and should have been removed, not rebuilt.
Updating system repos first, then checking on each AUR package marked updateable is the safer and more prudent thing to do.
3 Likes
because yay is a wrapper for pacman with the extended function for working with aur. And the whole point in a safe upgrade is to do the core system first and then aur and not everything at once (otherwise an error in 1 aur can mess with or prevent the whole system update)
5 Likes
Always make sure your official packages are updated first. That way, all of the shared libraries and compilers will be at the latest version when you have to rebuild packages from the AUR.
3 Likes
Ok, so you guys just don’t know how yay works.
You should try it, but the whole point is that I don’t need to tinker with multiple tools to keep my software up to date.
Rest assured, that yay will always update my core packages first, then extra, then multilib and only after all of that will check for AUR updates and rebuilds.
Interesting response considering I did not mention a user name or “moderator”
gitlab.manjaro.org - Packages / Extra / pamac/ Issues shows 11 issues reported in the last 4 years