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

Re: file: Access vs. Database stability

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-04-06 05:06:58 CEST

Ben Reser <ben@reser.org> writes:

> On Sun, Apr 04, 2004 at 06:55:51PM +0200, Jens-Uwe Mager wrote:
> > Well, tools like viewcvs do not use this level of the abstraction, they
> > use the direct level which just uses the OS path name to a Berkeley DB
> > directory structure. Same with the mailer.py or any other useful tools,
> > there appear to be no examples for the level of abstraction you refer
> > to.
> Both viewcvs and mailer.py use the python bindings. I can't say I've
> ever tried it but viewcvs and mailer.py should be able to operate on a
> URL just as much as they can a file URL. If they're taking and
> generating a file URL from the configuration and don't let you pass in a
> URL in directly then they need to be fixed...

If you've never even tried these tools, I would submit that voicing
opinions over how they should operate is kinda arrogant and fruitless.

Not every tool that accepts a filesystem path should also accept a
file:/// URL of that path. ViewCVS is a CGI script whose
configuration does happen to allow you to specify a filesystem path to
your repository (which works really well) or a URL to a repository
(which uses the RA layer, and doesn't work so wonderfully).

Mailer.py is written to be a server-side hook script, called by
post-commit with exactly the ${REPOS} argument provided to that script
by Subversion itself. Allowing a program like this to accept is URL
is silly, and will only lead to folks assuming that URLs other than
file:/// ones would be supported. Which, of course, they won't.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 6 05:11:03 2004

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.