RE: svn up --paranoid [was "Disabling automatic conflict resolution" ]

This is getting a bit off-topic, but ..

>> CVS has a 'watch/edit' facility, to aid communication. You probably
>> want that. SVN has no such thing yet.

That must be what I was vaguely remembering. I'm pretty unfamiliar with
CVS.

>> you'll see how most svn developers
>> feel whenever somebody says "but I *must* have locking!" :-)

I totally agree. I don't "*must* have" locking .. I need a way to
prevent multiple developers from modifying certain classes of binary
file. This is not quite the same thing.

The solution in my case is to not check in those binary format files,
but to convert them to textual form first. In fact, Microsoft provide
and use (even with VSS) an SCCTEXT program for just this purpose. This
makes it possibly to do DIFFs on the binary files for example. However
the conversion is one-way.

My plan is to mark svn:ignore VCX/VCT, SCX/SCT, FRX/FRT, MNX/MNT files
(they come in pairs) and only have the VCA/SCA/FRA/MNA files in the
repository. This will require a wrapper script to always generate the
ascii versions on check-in, and reconstruct the binary versions on
check-out, but should work perfectly. The only downside to this is that
check-outs will be very slow (this probably is why Microsoft didn't make
SCCTEXT two-way). I also might have trouble integrating this with VFP's
own source-control interface.

That said an advisory system would be jolly useful - when I've got a
moment I'll read the file you refer to. But I can wait for Subversion
1.1 (or 1.2 or 2.0...).

[P.S. could someone fix the Reply-to on this list? It is getting
annoying re-sending replies after discovering they went to the wrong
place! <g>]

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 19 01:37:38 2003