<br><br><div class="gmail_quote">2008/5/19 Tzafrir Cohen <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Mon, May 19, 2008 at 09:17:56PM +0200, Olivier wrote:<br>
> 2008/5/19 Tzafrir Cohen <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>>:<br>
><br>
> > On Mon, May 19, 2008 at 07:29:54PM +0200, Olivier wrote:<br>
> > > Hi,<br>
> > ><br>
> > > Today I'm building Asterisk using steps like this :<br>
> > ><br>
> > <a href="http://mikeoverip.wordpress.com/2008/03/29/asterisk-compilation-and-installation-on-debian-etch/" target="_blank">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<br>
> > > such as gcc, g++.<br>
> > ><br>
> > > As I'm trying to centralize everything (configuration files, source codes<br>
> > in<br>
> > > an SVN repository), I'm wondering if there is a smarter way to build<br>
> > > Asterisk.<br>
> ><br>
> > For configuration this is indeed very useful. For source: a bit less.<br>
> ><br>
> > Do you keep the whole Asterisk source tree in a subversion?<br>
><br>
> not at the moment but I'm wondering if we should ...<br>
><br>
> What do you<br>
> > do when a new version comes along? People tend to keep just patches and<br>
> > build instructions in the subversion.<br>
> ><br>
> > You can check the astlinux SVN repository for a working build system.<br>
> ><br>
> > We maintain the Debian Asterisk-related packages (and some others) in a<br>
> > subversion repository:<br>
> ><br>
> > <a href="http://pkg-voip.alioth.debian.org/" target="_blank">http://pkg-voip.alioth.debian.org/</a><br>
> ><br>
> > As you can see, most of the packages there have just a debian/<br>
> > subdirectory, where they keep the administrative files needed for<br>
> > packaging. Many of them also have the subdirectory debian/patches/ where<br>
> > patches to the source package are maintained.<br>
> ><br>
> > But some people keep saying that a a version control system that has<br>
> > better support for merging should allow you to store the source inside<br>
> > it and just merge new upstream versions (or rather: consider your<br>
> > changes as feature branches). This sounds cool, but may be tricky to<br>
> > implement.<br>
><br>
> I agree :<br>
> if we edit files somewhere, upload changes in repository and then download<br>
> them in target system, things are manageable<br>
> but it's easier to work directly on target system when tracking a bug or<br>
> tweaking some configuration. Then things become more difficult to handle<br>
<br>
</div></div>Hmm... give a second thought to a distributed version control system?<br>
<br>
(All the main contenders also happen to have much better merge support<br>
than subversion)</blockquote><div> </div><div>Do you mean git or equivalent ?<br>The fact is what kept us from using svn itself to save local modifications is that merge support was not very comfortable.<br><br>I think I should give a try ...<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="Wj3C7c"> Tzafrir Cohen<br>
icq#16849755 <a href="mailto:jabber%3Atzafrir.cohen@xorcom.com">jabber:tzafrir.cohen@xorcom.com</a><br>
+972-50-7952406 mailto:<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a><br>
<a href="http://www.xorcom.com" target="_blank">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir" target="_blank">iax:guest@local.xorcom.com/tzafrir</a><br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br>