bzr-windows team mailing list archive

[Adrian Wilkins <adrian.wilkins@xxxxxxxxx>]

John Arbash Meinel wrote:
> Adrian Wilkins wrote:
>> Not tested it yet (alas) and don't have the time at the present .. but
>> question :
> 
>> Is the installer still being bundled with the 1.5.6 Subversion
>> libraries? This affects the case where you ask Bazaar to manage SVN
>> working copies that have been created with SVN 1.6.x ; they are not
>> compatible with older wc libraries.
> 
> 
> Yes. There is a fundamental tension here.
> 
> Specifically, if we bundle the 1.6 libraries, they will *automatically*
> upgrade the working tree formats of any subversion working tree they
> encounter. 

Oh yes.

Mad idea ; the WC format number is written into the .svn folder ; it
should be possible to determine the format and load the appropriate
libraries at runtime (change the path?), or at least warn the user.

I too feel this tension, largely because of the time-lag between a WC
format going live in the CLI client, and it going live in Eclipse.

TSVN is up to date (and prompts the user to upgrade to newer versions of
the client in it's default config) ; so is SVNKit 1.3 ; JavaHL uses the
native binaries, so I reckon that covers Eclise, my other major SVN
client. My instinct says that the 1.6 WC format is probably current now.

Our internal servers are still at 1.4.6, because they work, and because
an upgrade to 1.6.x would mean upgrading Apache and all it's submodules
across a major version number, but I don't see such stumbling blocks for
the clients.



Which would mean that installing bzr 2.0 even to just test it
> out, would then require them to upgrade their existing subversion
> installation. (tortoisesvn, rapidsvn, etc.)
> 
> I would like to upgrade the libs at some point, I'm just being
> conservative because SVN has a policy of automatic upgrades of the
> working tree, and I don't think everyone wants to use bzr as the primary
> svn client.
> 
> John
> =:->
>