[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: use svn:externals for build/generator/ezt.py?

From: Russell Yanofsky <rey4_at_columbia.edu>
Date: 2003-10-31 04:52:37 CET

Greg Stein wrote:
> Today, we provide access to the SVN repository on port 80, port 81,
> and via SSL. The non-port-80 access points are primarily to get
> around broken proxies [which don't know DAV]. To a lesser extent,
> they are used to circumvent network security policies on users'
> (corporate) networks. The svn.webdav.org repository is only
> available on port 80 which might pose problems for some folks.

What is the problem here? Is it that svn:externals won't let users configure
a port number or that svn.webdav.org can't listen on other ports?

> The same issue will come up around referencing an external rcsparse,
> and apr(util) when they move into an SVN repository.
> One benefit is that we track the changing "upstream" components,
> although I don't expect a large rate of change for anything but
> apr(util), so this benefit might not be large.

If using svn:externals for APR would give subversion it's own private copy
of the library, is this desireable? I've just been using the APR that comes
with apache...

- Russ

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 31 04:50:04 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.