Re: sourceforge, nibs and other wrappers
Re: sourceforge, nibs and other wrappers
- Subject: Re: sourceforge, nibs and other wrappers
- From: Matt Neuburg <email@hidden>
- Date: Mon, 2 Sep 2002 13:34:22 -0700
On Mon, 2 Sep 2002 10:39:04 -0400, Bill Bumgarner <email@hidden> said:
>
> From: jerome LAURENS <email@hidden>
>
> I am using sourceforge to host a project, but how should I manage
>
> wrappers.
>
> It appears that cvs support at sourceforge does not recognize the
>
> cvswrappers shipped with mac os X, so something special must be done.
>
> What are the workarounds for this limitation?
>
> How should I manage the unwanted CVS folders when building my app?
>
>
There is a very easy solution to this problem: Don't use wrappers for
>
NIB files!
>
As such, simply add the NIB as a directory, then add the contents of
>
the NIB as normal, binary, files.
Actually, only objects.nib and/or keyedobjects.nib needs to be binary.
The tricks for getting started with CVS are as follows. Before importing,
set up your .cvsignore file to contain:
build
.DS*
*~.*
In this way during the initial import CVS won't dive into your build
directory, won't include the invisible .DS... files Mac OS X sticks
everywhere, and won't dive into the .nib backups that IB makes. That last
one is important because when IB makes a new .nib backup it overwrites the
existing backup completely, thus destroying any CVS info that's in there;
after that, of course, CVS is upset.
Now set up your .cvswrappers file:
objects.nib -k 'b'
keyedobjects.nib -k 'b'
*.tiff -k 'b'
*.gif -k 'b'
...and anything else you can think of that might find its way in there that
should be imported as binary.
Now do the import! Now archive and delete the original, tell cvs to give
you a new working folder, and you're off to the races. From here on in,
everything will work fine, and in fact it will almost work fine entirely
from within PB. In particular, PB will correctly check on the status of .c
and .h files for you; also as you create or add new files to the project
you can add them to cvs thru PB; and of course you can commit them from PB.
Another cool feature is that if you're in doubt of the state of things you
can have PB create a diffs file comparing the current state of a file and
its last committed state and show it to you in FileMerge.
However, PB doesn't understand what you've done with the .nib files, so you
also have to go the Terminal and do a cvs commit from time to time so that
the .nib files and what's in them get committed. Also there's no way to do
a tag in PB. So you'll still need to know how to run CVS from the command
line. Alternatively you can use CVL, a CVS gui wrapper from www.sente.ch,
which looks very promising (though I must admit I haven't used it much).
m.
--
matt neuburg, phd = email@hidden,
http://www.tidbits.com/matt
pantes anthropoi tou eidenai oregontai phusei
Subscribe to TidBITS! It's free and smart.
http://www.tidbits.com/
_______________________________________________
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.