Re: Xcode 3.0 and wrappers style handling of complex objects (i.e., nibs)



slashlos <slashlos@xxxxxxxxxxxxx> wrote:
I have made the voyage to 3.0 but find there's no longer an ocvs shipped
in the latest release. While I can fetch this, and cvswrap (which I
believe is needed to be in /Developer/... path) from 2.x, don't we want
to tread .nib 'files' as single objects? (I hope we still want/need to)

So just what are your choices when coming from a 2.x ocvs with wrappers
style development platform?

1. somehow hack with ocvs bits to work [yuck] and stay on 3.0

2. migrate to SubVersion or ? (which supports 'wrappers' style)
(this doesn't appear trivial judging by the cvs2svn, svnadmin, etc
route described in http://www.apache.org/dev/cvs2svn.html, or
http://cvs2svn.tigris.org/cvs2svn.html)

3. fall back and stay on 2.5 with ocvs

4. chuck SCM altogether in 3.0 for now.

5. Forget about wrappers, just check in nibs as directories.

I've been using CVS (and now svn*) for years without wrapping nibs.
They're just directories containing a small number of text or binary
files. There's no need to treat it specially. There used to be problems
with Interface Builder destroying the CVS or .svn directories in the nibs
when saving, but I don't believe that has been a problem since 10.2 or so.

* Having used both, I highly recommend switching to svn when you can. It's
not a revolution but it fixes a lot of annoying problems with CVS and in
general is much nicer to use. Some people will disagree but that seems to
be somewhat rare. Converting my CVS repository was a bit painful but not
too bad. I think the only big problem I had was that I had an "Icon\r"
file checked directly into the repository (I don't know why, as the
resource fork wouldn't have been preserved) and svn absolutely refused to
deal with the \r character. I ended up having to take it out of the
repository altogether before I could convert it.

--
Michael Ash
Rogue Amoeba Software
.



Relevant Pages

  • Re: Subversion/CVS experiment summary
    ... starting point for thinking about moving away from CVS. ... For me this is the biggest showstopper for FreeBSD development. ... But since the whole repository is versioned instead of individual files, ... Maybe we could see SVN as an equivalent to p4. ...
    (freebsd-hackers)
  • Re: Distributing Java Source
    ... If you're using SVN, you can just use the repository revision to refer to particular versions of the whole project (in CVS it would be necessary to tag every revision that you might be interested in referring back to). ... I still believe that Subversion is better, and many argue that distributed version control systems such as Git and Mercurial are better still. ...
    (comp.lang.java.programmer)
  • Subversion/CVS experiment summary
    ... This is an informal report on the viability of using Subversion to manage the ... to anyone who has looked at SVN before, ... I'm not trying to push one SCM over the other or suggest that CVS is ... Most of my tests were performed on the src/sys portion of the repository. ...
    (freebsd-hackers)
  • Re: Subversion vs CVS
    ... CVS beruflich und Subversion privat. ... Da kann man auch einfach mal einen Softlink im Repository setzen, um zwei Files an völlig verschiedenen Stellen gemeinsam zu versionieren. ... Svn hat keine brauchbaren eingebauten Berechtigungen. ...
    (de.comp.lang.misc)
  • Re: Datei wiederherstellen
    ... Für alles andere bietet sich die Verwendung eines CVS an, welches ein zurückgehen zu einer älteren Version erlaubt. ... Also ich bin mit SVN und TortoiseSVN sehr zufrieden, und wenn du nicht gerade ein Apache laufen hast empfehle ich dir, SVNService zu benutzen. ... Mit dem SVN Proxy sind dann die Funktionen der Quellcodeverwaltung im VS genau so nutzbar als wenn du VSS verwendest, abgesehen vielleicht von ein paar wesentlichen Unterschieden dieser Produkte. ... h. man muss eine Datei vorm Umbenennen oder verschieben nicht erst aus dem Projekt entfernen, im Archiv umbenennen/verschieben, dann neu abrufen und die Datei wieder ins Projekt aufnehmen. ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)