On Wed, Nov 25, 2015 at 10:03:56AM -0500, Leif Madsen wrote: > Absolutely! You would do that with an ENV (environment variable) setting in > the Dockerfile. Once that was setup, you can override that at build time > (basically you set a "default" value, and then you can override it from the > docker build command when you're building the container image). > > So phase 1 is actually already dead. I've been busy working on a > provisioning platform the last two weeks (on top of being sick), but I'm > through enough of it that I should be able to get to my phase 2 blog post > this week (ideally this afternoon). > > The preferred approach (as mentioned in my phase 1 blog post) is to > actually base on an RPM package. One of the issues was just trying to deal > with fedpkg (which is an awesome system btw) and getting custom changes, > and whatever version of Asterisk you wanted.
I personally prefer git-buildpackage. RPM support is now getting merged into the main tree. If you want to easily maintain patches in a patch queue in a git repository, it may come in handy. My current tree: http://git.xorcom.com/?p=rpm/asterisk.git Includes the Opus codec patch (thanks for all those who keep help maintain it). -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
