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

Re: Attention SVN client developers [Was: svn commit: r16244 ...]

From: Barry Scott <barry_at_barrys-emacs.org>
Date: 2005-09-28 23:00:02 CEST

On Sep 25, 2005, at 19:15, Branko Čibej wrote:

>> Why isn't this hidden inside the libsvn_client API?
>
> Because it has nothing to do with libsvn_client behaviour. It's a
> libsvn_wc thing.

That a detail of the libsvn_client implementation that I should not
have to care about.

>> Having all clients add this code is surely a bad thing?
>
> Unfortunately, there's no svn_wc_init() that clients are required to
> call, so there's no logical place to put this.

But you libsvn_client does get the config dir passed to it. You could
have placed this info into the
config file and then no client would have to change. Of course a client
that looks in .svn would
have to have an API to out the name of the admin dir.

>> That means that Trac, Rapidsvn, TortoiosSVN, pysvn and all users of
>> the
>> svn language binding have to change. And that will not all be reading
>> the dev list.
>
> Bindings presumably have their initialisation code where this could be
> put (for Python, at lease, I'd put it in the libsvn.wc modiule
> initialisation). So we can handle the bindings part.

Well if your design is to leave it up to the API user then no you
cannot place a workaround in the bindings without an override
mechanism.

> The others will just have to follow the dev@ list. You'll notice I
> also put this code into the minimal client example.

This is not a good advert for subversion. Its not programable unless
you follow svn dev...

Barry

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 28 23:00:59 2005

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.