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: John Clayton <email@hidden>
- Date: Tue, 4 Nov 2003 08:50:29 -0500
Hi Nicholas,
On Nov 3, 2003, at 10:04 PM, Nicholas Riley wrote:
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
So, it's good to hear that I'm not the only person to use this
technique. I assume you meant to say bundle a copy of CVS. True,
thanks.
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.
Ok, I haven't looked into MacCVSPro, but I will now. What do you mean
when you say attach MacCVSPro to cvs server. I'm lost there. But
maybe when I look over MacCVSPro that will make sense.
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.
I have similar sentiments, but the objective is not just to support
what I would use, but to assist folks in what they need to usewhich
all too many of us find is CVS. CVS is admirable for it's goals and
efforts, but perhaps by not supporting it one could encourage others to
switch. Probably not. I guess I could include it as legacy support and
provide tools to help the user switch to some other SCM system. I have
to consider this a bit more ....
Subversion is one possibility, but there are certainly others, both
open-source and commercial, depending on your needs.
Subversion support is already in the works. I like subversion and the
task should be relatively simpler since subversion has a well defined C
API.
Thanks, Nicholas
--
=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.
_______________________________________________
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.