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

Hi all,

Yesterday, I moved ezt.py into a Subversion repository in its own "mini
project". If we wanted to, we could start pulling ezt into the SVN working
copy via svn:externals.

   ( see http://svn.webdav.org/repos/projects/ezt/ )

My question there would be, "should we?"

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.

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. Another benefit is "eating our own dogfood"
for svn:externals. Negatives are as above.

Thoughts?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org