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

Ruby Bindings: Svn::Client::Context.info bug

From: Roman Zawada <info_at_zwadar.net>
Date: Sun, 29 Mar 2009 23:37:47 +0200

Hi,
it look's like Svn::Client::Context.info method is implemented in way
that prevents it from usage just on working copy without connecting to
server.
Doxygen documentation for svn_client_info2 tells that
/
If both revision arguments are either |svn_opt_revision_unspecified| or
NULL, then information will be pulled solely from the working copy; no
network connections will be made.

/but this rows in Svn::Client::Context.info

rev ||= URI(path_or_uri).scheme ? "HEAD" : "BASE"
peg_rev ||= rev

prevents NULL to be sent to svn_client_info2 method, so connection to
server is always performed.

Is there any way to workaround this? For now I've just commented rows
mentoined above, but would be nice to be able to use this funcionality
without modyfying or monkeypatching source code.

Also I've tryied to send Svn_opt_revision_t struct as revision to
svn_client_info2 method, but I'm unable to set kind.

revision = Svn::Core::OptRevision.new #(this works and responds to
method kind= )
revision.kind = Svn::Core::OPT_REVISION_UNSPECIFIED

crashed on
Uncaught exception: invalid type: Svn::Ext::Core::Svn_opt_revision_t

Thanks

__________ Informace od ESET Smart Security, verze databaze 3973 (20090329) __________

Tuto zpravu proveril ESET Smart Security.

http://www.eset.cz

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1474320

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-30 14:42:06 CEST

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

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