Re: Wrap CVS/Perforce for DVCS?
Re: Wrap CVS/Perforce for DVCS?
- Subject: Re: Wrap CVS/Perforce for DVCS?
- From: Andrew Pontious <email@hidden>
- Date: Sun, 9 Mar 2008 14:41:29 -0700
The problem with attempting to write a utility that would masquerade
as CVS, Subversion, or Perforce, is that Xcode currently relies on
quite a bit of the very nitty-gritty behavior of these utilities to
get its work done.
Just providing the documented simple features of the command-line
utilities might seem to be enough, but it will almost certainly not
work with Xcode.
If you're very determined and have a lot of time, you might be able to
reverse engineer the necessary behavior, but even then, it might break
in the next revision of Xcode.
-- Andrew
On Mar 7, 2008, at 8:26 PM, Nathan Vander Wilt wrote:
Xcode SCM plugin support has been mentioned as a
planned addition to Xcode through the years
(http://lists.apple.com/archives/Xcode-users/2004/Mar/msg00070.html,
http://lists.apple.com/archives/xcode-users/2007/Jan/msg00072.html).
The tools/documentation teams (quite understandably)
have a lot bigger things on their plate though,
especially now it would seem.
Does anyone know of any existing project that wraps an
unsupported SCM system as either Perforce or CVS (the
two supported systems with configurable executable
paths)? Getting to use DVCS is worth using the command
line for me, but I kinda miss having basic commit
support right inside Xcode.
For just a basic wrapper -- status, add/remove, diff,
commit -- can someone better familiar with version
control systems (I'm just a user) recommend which of
CVS vs Perforce would be the better one to use as an
interim wrapper around a DVCS like Bazaar or
Mercurial?
thanks,
-natevw
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden