Re: What's the best approach to integrating CVS support into an app?
Re: What's the best approach to integrating CVS support into an app?
- Subject: Re: What's the best approach to integrating CVS support into an app?
- From: Nicholas Riley <email@hidden>
- Date: Mon, 3 Nov 2003 21:04:02 -0600
- Mail-followup-to: John Clayton <email@hidden>, email@hidden
On Mon, Nov 03, 2003 at 08:58:20PM -0500, John Clayton wrote:
>
Hi,
>
>
I figure there must be at least three, but I'm too ignorant to really
>
guess at the best approach:
>
>
1) Run it as a task/thread and parse the output. I've tried this and
>
it's easy. I just don't like the feeling that a simple change in the
>
output from the CL tool could break my app.
This is what most people do. Since so many applications apply this
method, it's unlikely to break frequently. You could always bundle a
copy of the
>
3) Write a framework or other wrapper to the cvs source that let's me
>
use it directly. AFAIK, there isn't any way to do this as of now. Am
>
I wrong here? This I don't understand too well.
MacCVS Pro reimplements the CVS protocol itself, only for network
usage (rsh/ssh/pserver); you may be able to borrow code from there.
For local repositories you could just attach MacCVS Pro to 'cvs
server', for which the protocol is a bit better defined than the CVS
command-line client.
>
Well, that's all I can think of. Can anyone lend some guidance here?
4. Don't use CVS. Consider using some other protocol or SCM tool
which has a real API and doesn't require kludges such as the above.
Subversion is one possibility, but there are certainly others, both
open-source and commercial, depending on your needs.
--
=Nicholas Riley <email@hidden> | <
http://www.uiuc.edu/ph/www/njriley>
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.