Dear Linux Audio Conference friends!
We need your support for this year's conference .
Currently we are still looking for volunteers to help us with the
* Session Chairs - https://dudle.inf.tu-dresden.de/LAC18_Session/
* Stage Hands - https://dudle.inf.tu-dresden.de/LAC18_Stage/
* Camera/ Videomixer operators -
If you would like to support us, please provide your mail address and
to the corresponding dudle instance.
A short introduction/workshop for the different kinds of tasks will be
held on Thursday,
20180607 16:00 (CEST) (two hours before the Welcome Speech).
Your e-mail address will only be used by us to communicate with you
through a dedicated
mailing list, that will be disposed of after the conference.
The organizing team would like to thank you in advance, if you can spent
to help us with running the conference.
See you in Berlin!
Linux Audio Conference team
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:
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?