<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> ./debian/util.sh build-all -bn -z9 -v1<br>
<br>
</div>This would replace dpkg-buildpackage -b -uc ??<br></blockquote><div><br></div><div>Actually it more likely calls it for you (or git-buildpackage which'd call it in turn). Those are the debian tools for creating packages, that script'll call them for you as appropriate.</div>
<div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> mkdir -p /usr/src/freeswitch<br>
> cd /usr/src/freeswitch<br>
> git clone git://<a href="http://git.freeswitch.org/freeswitch.git" target="_blank">git.freeswitch.org/freeswitch.git</a> src<br>
> cd src<br>
> ./debian/util.sh build-all -bn -z9 -v1<br>
<br>
</div>How is that different than<br>
git clone -b v1.2.stable git://<a href="http://git.freeswitch.org/freeswitch.git" target="_blank">git.freeswitch.org/freeswitch.git</a></blockquote><div><br></div><div>It isn't - first four lines do the same, just to a different location.</div>
<div><br></div><div><br></div><div>The main advantage of my script incidentally is it uses mk-build-deps (from the devscripts package) to create and install a package that depends on all the build dependencies for building the freeswitch packages. That means you don't need to then install them yourself, and afterwards can remove that package then 'apt-get autoremove' to clean up your system, if you wish to do so.</div>
</div>