Yes, I know. But since I got those comments before today, I was wondering what others think of it. Personally, I am far from having any use of all the features of pacman or yay for that matter.
I am not sure how specialized my use is, but I prefer to separate them. There are far more (and more frequent) repo updates, so I use pacman for that (alias reduces typing). When there happen to be AUR updates too, I know of it, and I do a yay -Sua and try to pay extra attention! Also - I have a pkg that is ânewerâ than AUR, and I donât want anything to update it backwards⌠(1.12.2 â 1.11.3) - and yay -Sua allows for easy exclusion.
Does this make it specialized? Maybe Iâm just âspecialâ
Yeah, that sounds pretty specialized. Why do you have a package that is newer than AUR and why would it get updated backwards?
Then step it up and ditch pamac
I donât think thatâs the case. Manjaro might be a bit more bloated out of the box, but if that bloat is affecting performance so much that you can feel it, it shouldnât be too difficult to debloat it.
I installed the package with makepkg -si, after modifying the PKGBUILD to suit - and the default PKGBUILD still claims to be trying to install version 1.11.3. After my mods (which add cairo bindings and audacious libraries) it also builds 1.12.2 - almost a git version. So far no problems have resulted, so I havenât investigated further (though I probably should).
But the first thing yay
asks you (after updating the repo packages and starting the AUR update) is which AUR packages you want to exclude â for this exact reason.
A different way to do that which wouldnât create that problem is use a different package name and then add a provides
and conflicts
back to the original package. That way it would never get auto-updated with what is essentially a different package at that point.
Exactly - and as this unwanted upgrade would show up every time, I tend to pacman my updates unless something ELSE from the AUR needs an update too.
That wasnât quite what was relayed.
I had just stated you donât need to use an AUR helper when installing from the Endeavor or Arch repos.
@otherbarry explained why in greater detail.
No one specifically said it was preferred as if there was a right or wrong way to do an install.
Well, may be the reason is Gnome 40
Which is upto date on endeavour os
And not on manjaro
For me animations of Gnome 40 is faster on endeavour os
I sometimes use pacman
when Iâm installing packages from the repos specifically and Iâm not exactly sure of the name of the package, just because there tends to be less clutter on screen when searching for a package name. I see no other reason to use pacman
in parallel with yay
.
Right. I was actually referring to what @otherbarry said. My interpenetration of it was that they think pacman is a superior package manager for handling the repos and should be used over yay. That it is better to keep them sepearte. And the use of yay over pacman being put down to âpotential lazinessâ.
I must be out of the loop with what people are doing these daysâŚ
Next time it comes up ask for a practical example of in what way that is true. I have never had anyone give me one except for the weird edge cases.
Thatâs not really true, yay
simply runs pacman
commands. It uses pacman
to install repo packages, and also to install packages from the AUR that it builds (with the -U
option). There is nothing superior or inferior about that, itâs the exact same thing as running pacman
yourself.
You can see exactly what commands were executed by looking at the /var/log/pacman.log
file, there is nothing mysterious in there
It all just started with a user asking about the new app-info application referring to the example command given, that is yay -S eos-apps-info
and so off we went âŚ
If eos-apps-info
leads to interpenetration maybe we need to put on the list of controversial topicsâŚ
Well, âsuperiorâ was my wording to refer to:
For repo packages why would anyone not use pacman, and use an inferior tool with a subset of features? That makes no sense to me.
Which topic is all this magic in?
My answer is: why not? If you ever need those superior âfeaturesâ you always have pacman
, as it is a dependency of yay
. For normal regular use, I find the âinferiorâ yay
to be perfectly sufficient.
The misconception here is the underlying assumption that using yay
means not using pacman
, which is quite incorrect. yay
is a pacman
wrapper.
Are you sure? I thought it was linked to libalpm.