[arch-proaudio] What AUR build environment are you using?
Hi AUR packagers, which environment / tools are you using to build your AUR packages to ensure you don't miss any dependencies? I'm a bit confused on whether devtools can be used to build AUR packages in a chroot environment or if it is only for packages in the official repositories. Can somebody shed some light on this or link to a guide on how to do this? I tried this docker-based solution: https://github.com/Aisbergg/docker-arch-aur-makepkg It works for some packages, but I'm having trouble compiling e.g. the juce AUR package. I get some strange missing symbols in the linking stage, even though the needed library package seems to installed (icu). Does anybody have any experience with this solution? Or can anybody recommend an easy to use docker-based recipe for building AUR packages? Cheers, Chris
Hey Chris, On 2018-04-27 17:41:02 (+0200), SpotlightKid wrote:
Hi AUR packagers,
which environment / tools are you using to build your AUR packages to ensure you don't miss any dependencies? Currently I'm trying to switch to aurutils [1] as it has devtools integration.
I'm a bit confused on whether devtools can be used to build AUR packages in a chroot environment or if it is only for packages in the official repositories. Can somebody shed some light on this or link to a guide on how to do this? Yes, it can be used, but the dependencies need to be in a known repository and not be built from source.
I tried this docker-based solution:
https://github.com/Aisbergg/docker-arch-aur-makepkg
It works for some packages, but I'm having trouble compiling e.g. the juce AUR package. I get some strange missing symbols in the linking stage, even though the needed library package seems to installed (icu). Does anybody have any experience with this solution? Or can anybody recommend an easy to use docker-based recipe for building AUR packages? Not a big fan of docker, but whatever floats your boat :) Devtools uses systemd-nspawn, which is pretty great for building packages in a clean chroot environment.
Best, David [1] https://aur.archlinux.org/packages/aurutils/ -- https://sleepmap.de
On 2018-04-27 23:22:32 (+0200), David Runge wrote:
Hey Chris,
On 2018-04-27 17:41:02 (+0200), SpotlightKid wrote:
Hi AUR packagers,
which environment / tools are you using to build your AUR packages to ensure you don't miss any dependencies? Currently I'm trying to switch to aurutils [1] as it has devtools integration. Oh, I misread your mail a little I think. Usually I only use makepkg, but if all dependencies are in the main repositories I use devtools (`extra-x86_64-build`).
Additionally, if you have any dependencies, that you have in use multiple times, maybe I can move them to [community]? Best, David -- https://sleepmap.de
Am 27.04.2018 um 23:22 schrieb David Runge:
Yes, it can be used, but the dependencies need to be in a known repository and not be built from source.
So you can only build AUR packages, which do not depend on other AUR packages, with devtools? Is there a way around that?
Additionally, if you have any dependencies, that you have in use multiple times, maybe I can move them to [community]?
Eventually it would be convenient to have the "juce" package in Community, but it needs some work first (paths not conforming to standards). Chris
On Sun, Apr 29, 2018 at 03:34:18PM +0200, SpotlightKid wrote:
Am 27.04.2018 um 23:22 schrieb David Runge:
Yes, it can be used, but the dependencies need to be in a known repository and not be built from source.
So you can only build AUR packages, which do not depend on other AUR packages, with devtools? Is there a way around that?
As David said, if you have your deps built and in a repository that your local pacman instance points to, it will work. Alternatively, if you want a quicker / hackier way, you can do it like this: extra-x86_64-build -- -I ~/aur/cache/foo.pkg.tar.xz -I ~/aur/cache/bar.pkg.tar.xz This will install the foo and bar packages into the buildroot before building. You just need to build your deps in order, starting with the ones that don't need any other AUR packages. --Sean
Am 29.04.2018 um 19:48 schrieb Sean Greenslade:
As David said, if you have your deps built and in a repository that your local pacman instance points to, it will work. Alternatively, if you want a quicker / hackier way, you can do it like this:
extra-x86_64-build -- -I ~/aur/cache/foo.pkg.tar.xz -I ~/aur/cache/bar.pkg.tar.xz
Thanks, that did the trick. I was finally able to reproduce a problem with one of my packages (dexed) reported by a user. Now to find the cause and a solution... Chris
participants (3)
-
David Runge
-
Sean Greenslade
-
SpotlightKid