Olivier
2008-May-19 17:29 UTC
[asterisk-users] Which best practices to build and deploy Asterisk on different hardware ?
Hi, Today I'm building Asterisk using steps like this : http://mikeoverip.wordpress.com/2008/03/29/asterisk-compilation-and-installation-on-debian-etch/ As you can see, the first requirement is to download various dependencies such as gcc, g++. As I'm trying to centralize everything (configuration files, source codes in an SVN repository), I'm wondering if there is a smarter way to build Asterisk. What would you advise ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080519/ea54c6b7/attachment.htm
Matthew Mackes
2008-May-19 17:37 UTC
[asterisk-users] Which best practices to build and deploy Asterisk on different hardware ?
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <br> I recommend using Rpaths Asterisk Now distribution (and ignore the GUI) . My organization has been very happy with this Digium Supported- Pre Built Distro, which, is essentially Asterisk Business Edition. (Without the support contract)<br> <br> Matt<br> <br> <br> Olivier wrote: <blockquote cite="mid:442fbb120805191029r2857c24cp13f6413cc949dba5@mail.gmail.com" type="cite">Hi,<br> <br> Today I'm building Asterisk using steps like this :<br> <a moz-do-not-send="true" href="http://mikeoverip.wordpress.com/2008/03/29/asterisk-compilation-and-installation-on-debian-etch/">http://mikeoverip.wordpress.com/2008/03/29/asterisk-compilation-and-installation-on-debian-etch/</a><br> <br> As you can see, the first requirement is to download various dependencies such as gcc, g++.<br> <br> As I'm trying to centralize everything (configuration files, source codes in an SVN repository), I'm wondering if there is a smarter way to build Asterisk.<br> <br> What would you advise ?<br> <br> Regards<br> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ -- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: <a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a></pre> </blockquote> <br> </body> </html>
Steve Totaro
2008-May-19 18:31 UTC
[asterisk-users] Which best practices to build and deploy Asterisk on different hardware ?
On Mon, May 19, 2008 at 1:29 PM, Olivier <oza-4h07 at myamail.com> wrote:> Hi, > > Today I'm building Asterisk using steps like this : > http://mikeoverip.wordpress.com/2008/03/29/asterisk-compilation-and-installation-on-debian-etch/ > > As you can see, the first requirement is to download various dependencies > such as gcc, g++. > > As I'm trying to centralize everything (configuration files, source codes in > an SVN repository), I'm wondering if there is a smarter way to build > Asterisk. > > What would you advise ? > > Regards >Roll your own http://www.gnewsense.org/Builder/HowToCreateYourOwnGNULinuxDistribution Thanks, Steve Totaro
Tzafrir Cohen
2008-May-19 18:55 UTC
[asterisk-users] Which best practices to build and deploy Asterisk on different hardware ?
On Mon, May 19, 2008 at 07:29:54PM +0200, Olivier wrote:> Hi, > > Today I'm building Asterisk using steps like this : > http://mikeoverip.wordpress.com/2008/03/29/asterisk-compilation-and-installation-on-debian-etch/ > > As you can see, the first requirement is to download various dependencies > such as gcc, g++. > > As I'm trying to centralize everything (configuration files, source codes in > an SVN repository), I'm wondering if there is a smarter way to build > Asterisk.For configuration this is indeed very useful. For source: a bit less. Do you keep the whole Asterisk source tree in a subversion? What do you do when a new version comes along? People tend to keep just patches and build instructions in the subversion. You can check the astlinux SVN repository for a working build system. We maintain the Debian Asterisk-related packages (and some others) in a subversion repository: http://pkg-voip.alioth.debian.org/ As you can see, most of the packages there have just a debian/ subdirectory, where they keep the administrative files needed for packaging. Many of them also have the subdirectory debian/patches/ where patches to the source package are maintained. But some people keep saying that a a version control system that has better support for merging should allow you to store the source inside it and just merge new upstream versions (or rather: consider your changes as feature branches). This sounds cool, but may be tricky to implement. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir