Awebb wrote:It's in the PKGBUILD. Saying that you install a package from the AUR without even looking at the PKGBUILD usually confronts you with us zaelots, telling you that you should at least check the PKGBUILD for obvious problems before installing the package.
Hello everyone,I am new to Arch Linux (use Manjaro KDE at the moment), but I am trying to build and upload a new package to AUR.Tried it few times now with different errors. I have solved all, but now the last one doesn't let itself be solved.I don't believe I have a split package.
AnSnarkista, first of all, let me be the first to say, "Welcome to the Arch community!"Now, as mentioned in the PKGBUILD Request section readme, it is good practice (both for the sake of courtesy, and for your own sake in terms of learning) for you to at least attempt to write your own PKGBUILD before requesting one.
No offense, but that's horrible.Let's have some Arch-like simplicity here:Depend on gvim, because that's the official package. Put some explanatory comments in the PKGBUILD about vim-inteprete, advising users of that package to edit the vim-slimv PKGBUILD as required.
In order to test whether it would build and run if built against amule-daemon only, you would need to make a separate PKGBUILD for that as it's included in the amule package (as usr/bin/amuled) in the Arch repos. The AUR kamule PKGBUILD has amule as a dependency so you would need to change that to the new amuled or amule-daemon package.
Try a makepkg -s on it to see if there are any packages not in the official repo. Than check ccr to see if they are there. Otherwise search for individual parts of the package name; for example, many of the python packages in chakra use python2-something while arch uses python-something. If you find a matching package under a different name, change it in the PKGBUILD.