Arch Linux User Repository

PSA: I've started hosting this and all its dependencies as prebuilt packages (x86_86 only) in my repository for those that want to install them using pacman without messing around with building from the AUR.

@hytrax Does upstream Asterisk support opus transcoding at all? If so there may be an extra option that needs to be set at build time. I'm happy to consider adding it if it doesn't incur more dependencies than the default. Let me know if you figure out what it is.

@caleb I have built it with the PKGBUILD and Opus passthrough support seems to be there but it cannot transcode from, say, G.722 to Opus. "core show translation" does not list it.

@hytrax The build in my user repository is compiled with the PKGBUILD exactly as posted here (most recently updated by me). There is a dependency on opus so I would have expected it to be found at build time and support to be built in. Do you get something different when you build this PKGBUILD yourself?

It's possible they changed something in recent releases and we need to explicitly enable support now, but I missed anything about that in the change logs.

Is it not compiled with opus enabled? If I use the package form the alerque repo the opus modules are missing and thus transcoding does not work.

@post-factum Thanks for the heads up. It's building now, if it looks like it runs alright I'll post the update shortly.

Thanks for the heads up @Thulinma, updated package coming shortly.

Hey there! Asterisk no longer installs headers by default, but dependent packages expects them to be installed. To re-enable headers, simply add the line:

make DESTDIR="${pkgdir}" install-headers

after the existing line

make DESTDIR="${pkgdir}" install

And that'll do the trick.

@nkukard Have you ever messed with fixing this build so it works with Lua 5.3 instead of 5.1? Asterisk supports it, their configure.ac just detects it in the wrong order. I messed with patching it some but didn't get it quite working. I wondered if you'd tried to go down that road before.

I've not tired that myself, I'd prefer to stick with what Asterisk detects, but as you say its in the wrong order, so I think it should be fine to change it if you want.

Also I don't think that should be an optdepend because it cannot be added or removed by installing Lua after the fact, it has to be build in, which means it has to be there at build time. I think it should be a makedepend, and the Arch configuration should just support it out of the box. This is consistent with the way many many other packages that optionally have Lua support handle are handled. Would you mind if I flip that around like that?

Agreed, feel free to flip that around :)

@nkukard Have you ever messed with fixing this build so it works with Lua 5.3 instead of 5.1? Asterisk supports it, their configure.ac just detects it in the wrong order. I messed with patching it some but didn't get it quite working. I wondered if you'd tried to go down that road before.

Also I don't think that should be an optdepend because it cannot be added or removed by installing Lua after the fact, it has to be build in, which means it has to be there at build time. I think it should be a makedepend, and the Arch configuration should just support it out of the box. This is consistent with the way many many other packages that optionally have Lua support handle are handled. Would you mind if I flip that around like that?

Thanks for the add @nkukard. I've also added you to pjproject as it is the only other required dependency for this that is in the AUR. That way any future absence I make have won't hold up updates to this package ;-)