Hello community,
I’m new with Arch Linux and testing CachyOS on my ASUS TUF.
Before I had installed “Manjaro” and I was able to install “NordVPN”.
If I check the CachyOS paket-installer, I cannot find the NordVPN Arch file here.
Sorry for beginner question. But is there a way to get NordVPN from Arch and if so how can I installing this packet in CachyOS?
You can install it with the console command
paru -S nordvpn-bin
From there you can set it up using this webpage
Thank you, works perfect.
Does this packet will be updated, or I have to do manually?
I suppose nordvpn-bin was installed from AUR - AUR (en) - nordvpn-bin
If the package will be updated by maintainer of the AUR package (Last Updated: 2024-11-28 13:50 (UTC), your package will be updated automatically during standard update process if you use paru manager and not pacman.
paru -Syu
That does not work for me. My console for whatever reason does not recognise “paru”.
Paru was replaced by yay.
yay is also not known
Does CachyOS no longer have a Pacman wrapper/AUR helper?
It uses shelly as the default. If one prefers paru or yaythey can install it.
This was never true so I do not know where it comes from.
It has pacman because even those that pretend to have something better still rely on it in various ways (pamac too).
But as for an aur-helper included by default? I guess that is shelly now. But like pamac it is not a pacman-wrapper so has various problems even when it is working exactly as designed.
I do have to say its a bit concerning we have so many of these “but it says I do not have X program - what could I possibly do in this situation?” not only being common .. but common within the context of managing foreign software.
Anyone trying to interact with the AUR should understand basic package management.
As well as concepts like “aur-helper” and so on.
( Technically the old advice was that one should be able to do these things manually, using makepkg before using the AUR. So for example there were no aur-helpers in the repos .. you would need to first understand how to git clone and build the helpers yourself before being able to use them. )
And then they should still read every single PKGBUILD.
If you cannot do this you should not use the AUR.
That sprang from my childhood imagination 
I read an announcement stating that paru was being dropped… I should have kept reading.
I’m not familiar with shelly yet, as I haven’t had a need for it. But since it’s a standard tool, I really ought to get to know it.
There is one thing I’m fairly certain about: CachyOS won’t make the same mistake Manjaro did.
Are we sure about that?
Shelly is a single app written (supposedly .. I am still not sure it was not largely vibed) by a single individual that none of the core team is directly involved with, and it attempts to use ALPM directly instead of being a wrapper for pacman.
All of those things are true of pamac and are parts of why it is awful.
Shelly also has the extra distinction of being even newer with even less testing and its not even built using linux native technology - its C# thats C-Sharp.. the windoze bastardized form of C that is not really C and intended for dotNet (another windoze tech).
I guess we have not yet had complaints that shelly is constantly DDoSing the AUR. Though Pamac does not either anymore - by using a cache it can DDoS instead because it never fixed the real issue. 
Anton seems pretty involved from Cachy and there are 2 other individuals committing most of the code. I agree the development velocity and amount of refactoring feels a bit crazy.
They do occasionally implement or talk about implementing actual useful things. Still don’t particularly trust it though.
In some ways that may be better but its early days so its actually somewhat similar so far.
“Talking with” the team somewhat actively is still not direct involvement.
And its still a little unclear where this relationship even came from. Like did the (at the time) 1-month old tool just get posted, and liked immediately?
Anyways a sort of informal communication between a detached person and the real team would have been the case with pamac as well. Eventually you had a few commits from others but they were minimal like version name bumps. Otherwise the main dev came from a single unrelated person and then when they, for example, went back to university, then any glaring issues with pamac would go unfixed for months.
It could very well be that shelly ends up in the same kind of situation. Maybe not.
I guess I just wonder about a few of these things.
Initially I was mainly responding to the idea of ‘not doing the same thing’ because frankly, as I have said elsewhere, this has a sort of ominously similar feeling to me.
I will continue to use and suggest what I know to use and suggest.
We may just end up with the ‘official’ manager being Shelly while experienced users in the forum advise something different. Which is still where manjaro+pamac are at I think.
Or maybe I will be surprised and shelly will be great for everyone. I suppose thats possible too.
He’s contributed maybe 20% of the commits over the past 3 months.
I think the main dev networked on the cachy discord or something.
To be fair I rather prefer a package manager that goes months between releases…beause it just works.
Just to be clear - I was not trying to pronounce some sort of known problem with the development or relationship or some such. Just that I neither have a proven reason to believe it will end up being substantially different than that other experience.
And thats really just as in the interest of Cachy users more generally.
The kind of application does not interest me personally in any case.
Cachy decided, and I think this was a bad decision, to ditch paru in the recent ISO and double down on Shelly due to the AUR issues of people not doing basic due diligence.