Fran Fabrizio writes:
>
> So, I was wondering, if we were to use their latest tarball as the base
> of our CVS (first question: will there be a problem having a CVS project
> that large?) and then edit and check in our changes off of that, I think
> that would work, with a few questions.
Yes, that's the right approach, and there shouldn't be any problems with
a project that large as long as you have enough disk space to hold it.
> - What happens when they release a new tarball? We've already made
> changes to some of their stuff so do I create a new vendor branch, put
> their new stuff on it, and then merge the branches?
You import it on the existing vendor branch and then merge it with your
local changes. See:
http://cvshome.org/docs/manual/cvs_13.html#SEC104
> - Is there any way to check in the whole project at once if there are
> binary files in it?
If you really mean checkin, that just works automatically. If you mean
import, then you'll have to use the cvswrappers file or the -W option to
import to specify which files are binary. See:
http://cvshome.org/docs/manual/cvs_9.html#SEC80
> - Will I have to change all of the 100+ (rough estimate) Makefiles so
> that they compile somewhere else instead of right there in the working
> directory?
You shouldn't -- CVS automatically ignores most generated files and you
can always create .cvsignore files to have it ignore more things.
-Larry Jones
Hmph. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
