Hi,
Yesterday I built megasync from AUR using pamac.
https://aur.archlinux.org/packages/megasync
There were dependencies missing: autoconf, automake, patch and make
could you please add these dependencies to the AUR process?
or better yet the base-devel dependency?
thanks
JPT
Welcome to the forum! 
Manjaro does not maintain the AUR. The AUR is an independent repository with build scripts uploaded by Arch users. Manjaro offers access to the AUR — for users who know what they are doing — via pamac and yay, but that’s where our support ends.
Those should normally be included in the base-devel package. The base-devel package is however not installed by default.
They already are. But it won’t install itself.
Similar comment was posted on AUR yesterday
JPT48 commented on 2024-03-04 18:51 (UTC)
Hi, please add these dependencies: patch, autoconf, automake, make
or better, the build-essentials package, whatever it’s name actually is on arch.
thanks
FabioLolix commented on 2024-03-04 18:52 (UTC)
@JPT48 installing the base-devel package is a pre-requistite for using the AUR Arch User Repository - ArchWiki
$ pamac info base-devel
Name : base-devel
Version : 1-2
Description : Basic tools to build Manjaro Linux packages
URL : https://www.manjaro.org
Licences : GPL
Repository : core
Groups : --
Depends On : archlinux-keyring autoconf automake binutils bison debugedit fakeroot file findutils flex gawk
gcc gettext grep groff gzip libtool m4 make manjaro-keyring pacman patch pkgconf sed sudo
texinfo whichI my opionion, if you provide an installer for AUR packages then this installer should deliver all dependencies that are neccessary for basic usage of AUR packages.
You can create your own distribution then and provide that. I would go as far as making an exam about understanding of AUR you have to take before you even get an option to build anything.
The pamac package manager offers support for accessing the AUR, but it’s not enabled by default, and there is a reason for that. Manjaro has no control over the AUR, any more than that we’d have control over Snaps, FlatPaks or AppImages. But pamac can access those repositories too, if enabled.
Therefore, Manjaro does not recommend the use of those repositories unless one knows what one is doing. Needing to install the base-devel package is considered “knowing what you’re doing”.
I generally agree that such things can install automatically (like toggling snap for example installs the snap service). But manjaro is a small team distro, only one man codes pamac so this is a low priority task.
But there is also a target conflict here: the more one click the experience, the less tech savvy users will use the distro. And no matter how one-clicky it becomes, an arch based rolling distro will never be really suitable for absolute beginners. So at the end of the day, there will just be more complaints. We already see this in other areas of the OS: the gui for kernel install clearly states what is recommended, yet people install non-lts kernels and forget to remove them in 3 months. Or even RT kernels, just because they have a higher number. If they had to use the command line, some of these people would not have bothered to install unsuitable kernel without reading what it is and would have stuck with the defaults.
Option to enable AUR support in pamac GUI Preferences > Third Party follows 2 warning messages
AUR is a community maintained repository so it presents potential risks and problems
All AUR users should be familiar with the build process
User is responsible for installing base-devel package to provide AUR build dependencies
OMG! You mean, they actually have to read what it says in the warnings? 
No point in keeping this open. The issue has already long been properly addressed. 