Re: Wrap CVS/Perforce for DVCS?
Re: Wrap CVS/Perforce for DVCS?
- Subject: Re: Wrap CVS/Perforce for DVCS?
- From: Nathan Vander Wilt <email@hidden>
- Date: Mon, 10 Mar 2008 13:28:29 -0500 (CDT)
--- Andrew Pontious <email@hidden> escribió:
> 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.
I know just enough version control to get by, so I'm
glad I didn't have time to start over the weekend!
Thanks for the discouragement - better to know in
advance what a can of worms I'd be opening than to
start discovering such things when I "almost have it
working".
> 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.
That would put me in the same boat as
reverse-engineering the existing plugin interface, and
life's too short... There are *many* fine Disributed
Version Control systems gaining popularity, so tacking
just one in via unsupported means is not worth the
time away from actual programming. If that were the
goal, I'd still be using CVS! :-)
I'll keep waiting and hope enough others will chime in
over at the bug reporter to make worth the team's
investment.
thanks,
-natevw
> 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
>
____________________________________________________________________________________
¡Capacidad ilimitada de almacenamiento en tu correo!
No te preocupes más por el espacio de tu cuenta con Correo Yahoo!:
http://correo.espanol.yahoo.com/
_______________________________________________
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