This is brought up every once in a while, even this week, generally by folks who do no understand any of these structures … and the answer is always no.
The AUR is not supported, and there are no intentions of somehow ‘mirroring’ it or otherwise.
The AUR is quite literally the Arch USER Repository - it is where ANYONE can create and post a PKGBUILD. It is FOR ARCH, and it is entirely 3rd party.
Interacting with it in any way is your own responsibility.
Semantics is thus.
But … how about I put it another way … the AUR is the closest you will get to a reasonable equivalent of ‘download the exe from a website’ - but provided by users.
It is compatible with Manjaro (more so if you know what you are doing) … but it is still ‘outside the jurisdiction’ so-to-speak. Making package management tools more able to handle them for end-users is not a bad thing in my opinion, though that is a hotly debated topic.
Help my position in the argument by learning WHAT THE AUR IS and how to use it.
Agreed - as much as anti-manjaro spam will attempt to say otherwise … every single bit of software and documentation that touches it goes through leaps and bounds to point people to the upstream, makepkg, and the whole ‘unsupported’ mantra.
But hey - half the forum wouldnt exist if it werent for these persistently reoccurring queries.
Pamac as single app/tool/instument supports interactions with AUR.
Manjaro team and Community are not supports any AUR-relataled issues, sometimes they could dive in it just as general interest of out-of-their-stuff issues, but it is out-of-Manjaro staff support: it is user, pamac developer, AUR package maintanter related issues.
Is that close to what we all are talking about?
If “yes” than consider do not cut “by the Manjaro team and Community” phrase after
and after not so clear enough
So support by (any app: pamac, yay, etc.) and by (Manjaro team and Community) are different things. That’s the point?
Don’t mean to interject in the middle of an argument but can someone explain, from a technical perspective, why pamac occasionally fails to grab aur updates that are seen by yay and why loading development package updates on pamac is very, very slow (and also often misses some yay-visible devel updates)
I don’t have alot installed from the AUR but since the issues with search in Pamac I’ve been using pamac upgrade in the terminal and Google Chrome and and all the others have upgraded and are working just fine for me.
Any way to list only items I have installed or built from the AUR? I want to see if they can be replaced. Yesterday I had to do two sets of updates to grab everything that needed to be updated and I should have had to do that. It’s one thing to have to tell Pamac to search AUR instead of having it search AUR on each character typed, but another to have updates affected.
As soon as you have AUR enabled, even just for fun, we did also search the AUR with every letter you typed
With the newer 10.2 release series we also added auto-suggestions to the AUR
This all resulted again into a DDOS, which brought the AUR down
Sadly we made 3rd party software “repositories” a first citizen in Manjaro and Pamac itself. Sure it is nice for the user to have a global search result on all major Software platforms at once. This is how we designed it. However, if a platform can’t handle our extra request rate we have to take action. Sometimes those can be more radical.
Requests within 6 hrs when AUR went down …
So either our user agent is totally blocked by the Arch Servers, which would mean Pamac for Manjaro won’t work with the AUR at all (other distros using Pamac, would still btw.) or we reduce the user experience in the graphical UI. You can still use Pamac as regular AUR helper in CLI mode, in which we didn’t change anything.
So follow this issue, be constructive and be sure that we work closely with AUR developers to get this sorted out.