> - If you want to work on Mac OS X, be sure to interoperate with working
>copies checked out by the command-line client. One big glitch I see with
>MacCVSPro (and I expect the same from MacCVSClient) is that it, having
>reinvented the CVS client, keeps CVS meta-data in resource forks and so
>on, which /usr/bin/cvs uses those goober CVS/ turds in the working copy.
This definitely an issue in CVS. When basing an SVN client on
the SVN libs, this is taken care of automatically, no?
I was also pondering, what the 'correct' line endings in Mac
OS X text files are. Is it the old Mac OS style or UNIX style?
Will SVN do line ending conversion for text files? It should,
>On Mac OS X, you will want to use the SVN library for all SVN operations
To write a Mac OS SVN client should be much simpler a task once
the SVN libraries are ported to Mac OS than was to write a
CVS client here.
>so that both the GUI and command-line clients play with each other's
>working copies nicely, even if you end up stuck with SVN/ turds, though
>I suppose you can get away with marking them invisible. :) That wasn't
>really an option with CVS, having no library, but it should be done here.
Well, remember the turds discussion? An idea was to have the
option to keep folders turd-free and store the turds in
question in parent (or grandparent ...) SVN folders. All this
would then sit in the SVN libraries, though and thus wouldn't
be a Mac OS specific issue.
> - And that means, that if you want the same client in Mac OS 9, we'll
>want libsvn ported to Mac OS 9, which probably means APR on Mac OS 9,
>which I know Ryan is interested in seeing happen, but may be a fair bit
Thanks for putting this in simple terms here. That kind of
thing was what I had expected, but didn't know enough about
APR to quantify the effort (if we take "a fair bit of work"
as a quantification... ;-)
> I might be game for taking a stab at an application in my free time
>(heh), but I'd do in using Cocoa (in Objective-C), which won't work on
>Mac OS 9 at all, unfortunately.
I'd hope there'll be a "classic" version (Mac OS pre X) as
well. Once the SVN libs, APR, etc. compile on Mac OS, I'd
be interested in contributing to this.
It would be great if the Cocoa and "classic" versions would
behave the same and have the same UI layout as far as that's
possible so that people can switch easily. This would also
help writing user documentation for both clients at the same
They can take away my Mac when they pry
my cold, dead fingers from my mouse.
Received on Sat Oct 21 14:36:15 2006