Proper way to migrate IB 2.0 NIBs to 3.x?

slashlos <slashlos.DeleteThis@optonline.net> writes:

> well I bit the bullet and went the xib route. Now is there a clean way
> to have cvs not fetch my old nib files? I'd removed them all by
>
> cvs remove -Rf *nib
>
> but they persist!

The problem is that CVS doesn't really want to delete directories. You
can tell it to ignore empty directories on an update or checkout, with
the -P option:

cvs update -P foo

sherm--

--
My blog: http://shermspace.blogspot.com
Cocoa programming in Perl: http://camelbones.sourceforge.net

In article <m1eiu2o73o.fsf.TakeThisOut@dot-app.org>,
Sherm Pendley <spamtrap.TakeThisOut@dot-app.org> wrote:

> slashlos <slashlos.TakeThisOut@optonline.net> writes:
>
> > well I bit the bullet and went the xib route. Now is there a clean way
> > to have cvs not fetch my old nib files? I'd removed them all by
> >
> > cvs remove -Rf *nib
> >
> > but they persist!
>
> The problem is that CVS doesn't really want to delete directories. You
> can tell it to ignore empty directories on an update or checkout, with
> the -P option:
>
> cvs update -P foo

Also consider upgrading to something newer. At least to subversion,
which would be a mostly painless migration from CVS.

--
Tom "Tom" Harrington
Independent Mac OS X developer since 2002
http://www.atomicbird.com/

Tom Harrington wrote:

> Also consider upgrading to something newer. At least to subversion,
> which would be a mostly painless migration from CVS.

sightly off-topic:
--
I keep meaning to look into this; is the x/code interface the same? I
see there's an svn and svnadmin so it's similar but is there a history
migration tool from cvs?

Right now I used the instructions to access cvs via ssl which work fine
so I'd need a similar access for svn; it seem doable but the thought to
the migration halts me. I use one base system and a few client laptops.

Is there a tool that would do this (presume existing cvs repository at
/usr/local/cvsrep)

cd /usr/local
sudo mkdir svnrep
<some-tool> cvsrep <migrate-enmasse-to> svnrep

There are several projects involved so I'd keep cvs around [probably
forever] just in case.

--
/los "I was a teenage net-random"

In article <4a288196$0$22516$607ed4bc@cv.net>,
slashlos <slashlos RemoveThis @optonline.net> wrote:

> Tom Harrington wrote:
>
> > Also consider upgrading to something newer. At least to subversion,
> > which would be a mostly painless migration from CVS.
>
> sightly off-topic:
> --
> I keep meaning to look into this; is the x/code interface the same? I

I couldn't say if they're the same, as I've long used the command-line
interface for both. I believe they're intended to work similarly.

> see there's an svn and svnadmin so it's similar but is there a history
> migration tool from cvs?
>
> Right now I used the instructions to access cvs via ssl which work fine
> so I'd need a similar access for svn; it seem doable but the thought to
> the migration halts me. I use one base system and a few client laptops.
>
> Is there a tool that would do this (presume existing cvs repository at
> /usr/local/cvsrep)
>
> cd /usr/local
> sudo mkdir svnrep
> <some-tool> cvsrep <migrate-enmasse-to> svnrep
>
> There are several projects involved so I'd keep cvs around [probably
> forever] just in case.

There's a CVS->SVN migration tool at <http://cvs2svn.tigris.org/>.

There are a lot of other source-control systems available these days,
and I don't know if I'd say that SVN is the best. But it's certainly an
improvement over CVS, and was designed to be familiar to CVS users, so
it should be the easiest one to adopt.

--
Tom "Tom" Harrington
Independent Mac OS X developer since 2002
http://www.atomicbird.com/

Well I took the plunge and went the subversion route.

While the conversion tool, cvs2svn, was pretty painless once I'd gotten
it built ok, the setup was a bit daunting.

For os/x 10.5.5 you need at least python 2.6(I used 2.6.2 with dmg
packaging) a new gdbm 1.8.3; something about the shipped python (2.5.1)
didn't work or wasn't built to support the tool due to gdbm, blah blah
blah. I obtained instructions to build both but it took a couple tries
to get python properly setup; seems to be two places where frameworks
get put:

/Library/Frameworks and
/System/Library/Frameworks/

and paths for CLIs

/usr/bin
/usr/local/bin

You'll know you're there if you can "cvs2svn --help". I did it in the
repository host using 'sudo' to create the root path; technically I use
paths like

svnrep.0
svnrep.1
...

then use a soft link to the latest. As suggested I created a backup and
it was pretty painless after that but I did notice some slight nits:

o various paths under the svn repo need to have their modes set;
this might just be me as I prefer to use group vs. a single user
permissions; group write for my uses was needed;
found a web page tutorial

o the xcode ssh linkage I'd used before for cvs worked fine!, once I
figured out what to enter into the repository dialog:

name: my svn repository
URL: svn+ssh://remote-host:/usr/local/svnrep
Scheme: svn+ssh
Path: /usr/local/svnrep
Port: <blank>
User: slashlos (or yours)
Password: <blank>

o the size of the working directory is nearly double that of cvs!

The really nice thing was finding a good gui, svnX. Xcode usage appears
slightly different.

Oh, and no .nib files! I left cvs intact (never delete information) just
in case. , and promptly burnt all to a cd-rw. Thanks!

--
/los "I was a teenage net-random"