On 2/22/06, Jim Blandy <jimb@red-bean.com> wrote:
> On 2/22/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> > Honestly, I don't care one way or another if they can --force it or
> > not. Checking out trees that large puts an unacceptable amount of
> > strain on a public resource in this case, I just want to be able to
> > stop them from making silly mistakes that require administrator effort
> > to block, and reserve the admin effort for the cases where people are
> > actually doing this kind of thing on purpose. If they can add --force
> > and make it work, that's nice, but it's not really a showstopper IMO.
>
> It seems to me that there are several ways this problem can come about
> for which an administrator could plausibly want different policies.
>
> Wanting to prevent accidental checkouts of the root by users who don't
> understand the repository organization seems like something almost
> every Subversion installation would want to do. If the protection was
> done in a way that wasn't too confusing to new users, I'd say it
> should be on by default.
>
> Wanting to prevent root checkouts by search engine robots seems more
> like a site-by-site decision.
Just to be clear, the search engine we had a problem with at
svn.apache.org was actually doing a checkout of big chunks of the
repos, not just crawling the http interface like you'd normally
expect. Normal http crawlers can be dealt with via robots.txt, so I
don't see any reason to build in support for blocking that sort of
thing in subversion itself.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 23 01:16:58 2006