On Fri, Mar 7, 2008 at 7:10 PM, Stefano Kismet Lenzi
<kismet.sl_at_gmail.com> wrote:
> Mark Phippard-3 wrote:
> >
> > On Fri, Mar 7, 2008 at 4:50 AM, Stefano Kismet Lenzi
> > <kismet.sl_at_gmail.com> wrote:
> >
> >> Are you planning to support in any way SVK
> >> (http://svk.bestpractical.com/view/HomePage) ?
> >
> > SVK is its own version control tool that just happens to use a SVN
> > repository for a local data store. There is otherwise no synergy
> > between it and a standard SVN client. An SVK plugin for Eclipse would
> > have to be its own product entirely. For example, SVK has its own
> > working copy format and commands. It does not use the SVN API for
> > those layers.
> >
> > So ... no.
> >
> >
>
> Ok! I agree with your vision. My idea was based on a scenario were a user
> uses SVK merely as SVN client by mirroring SVN repo with SVK thus saving
> space and time when the user have to perform common operation like: diff
> among version, log inspection, etc. In this scenario the integration of SVK
> inside subclipse will the mapping of standard SVN command over the SVK ones.
The problem is that the SVK client does not use SVN at all. It only
uses the SVN repository and has code to push/pull with another
repository. An SVK checkout/commit etc. is all custom code. So you
are pretty much starting from scratch if trying to integrate it with
Eclipse. All of the SVN API calls we make to run our client would
just fail with an SVK working copy.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-03-08 01:33:28 CET