Thanks Trent i will give this a go. On the seond co did you not mean to checkout the apr-util/trunk ? or do i need to checkout apr twice ?
"Trent Nelson" <[EMAIL PROTECTED]> 12/21/2006 07:51 AM Please respond to dev@httpd.apache.org To <dev@httpd.apache.org> cc Subject RE: Apache BUG: 36495 : ajp_proxy_connect_backend failure > Here's how I build trunk: > > $ mkdir -p apr/apr > $ mkdir apr/apr-util > $ mkdir -p httpd/trunk > > $ cd apr/apr > $ svn co http://svn.apache.org/repos/asf/apr/apr/trunk > $ cd ../apr-util > $ svn co http://svn.apache.org/repos/asf/apr/apr/trunk > $ cd ../../httpd > $ svn co http://svn.apache.org/repos/asf/httpd/httpd/trunk > I'll be happy to push the above into a page under httpd.apache.org/ > dev as "here's how to build HEAD for testing" if folks think it > useful. Or I may put it on my blog. I find that svn externals can provide a useful alternative to the approach you've mentioned: F:\scm\svn\svn.onresolve.com\contrib\trunk\httpd\trunk>svn pl -v Properties on '.': svn:externals : src http://svn.apache.org/repos/asf/httpd/httpd/trunk src/srclib/apr http://svn.apache.org/repos/asf/apr/apr/trunk src/srclib/apr-iconv http://svn.apache.org/repos/asf/apr/apr-iconv/trunk src/srclib/apr-util http://svn.apache.org/repos/asf/apr/apr-util/trunk src/srclib/zlib https://svn.onresolve.com/contrib/tags/zlib-1.2.3.1 src/srclib/openssl https://svn.onresolve.com/contrib/tags/openssl-0.9.8d.1 src/modules/contrib/mod_auth_sspi https://svn.onresolve.com/contrib/tags/httpd-mod_auth_sspi-1.0.4-2.2.2.1 /src Tell you what would be nice: svn.apache.org/repos/asf/httpd/httpd/views/ trunk/ 2.0.x/ Where each 'view' is simply an empty directory with the relevant svn externals set for building that particular branch. That way, all you'd need to do to get a buildable trunk is: svn co http://svn.apache.org/repos/asf/httpd/views/trunk Trent. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
