When you say Mac OS, watch out for Mac OS X. I expect that I'll be
able to get the SVN command line ported to Mac OS X without much
trouble. I need to do APR in any case for Apache 2.0.
Note that if you Windows guys want some good ideas from existing CVS
GUI clients, MacCVS Pro (from Netscape) is pretty well liked by many
people I talk to. I hear that MacCVSClient is also good stuff. There is
also a Cocoa CVS client called CVL for Mac OS X which has come cool
ideas in it, though I've not found it to be complete enough for my liking.
Those of you interested in a Mac OS port should consider a few things:
- If you want Mac OS 8 and 9, be sure to play nice with Carbon so you
can bring that code to Mac OS X.
- 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.
On Mac OS X, you will want to use the SVN library for all SVN operations
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.
- 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
of work.
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.
-Fred
Wilfredo Sánchez, wsanchez@apple.com
Open Source Engineering Lead
Apple Computer, Inc., Core Operating System Group
1 Infinite Loop, Cupertino, CA 94086, 408.974-5174
Received on Sat Oct 21 14:36:15 2006