This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: warning about classpath import
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <tromey at redhat dot com>
- Cc: "'GCJ Hackers'" <java at gcc dot gnu dot org>,"'GCC Mailing List'" <gcc at gcc dot gnu dot org>
- Date: Thu, 22 Sep 2005 15:41:33 +0100
- Subject: RE: warning about classpath import
----Original Message----
>From: tromey@redhat.com
>Sent: 22 September 2005 15:25
>>>>>> "Dave" == Dave Korn <dave.korn@artimi.com> writes:
>
>>> I'm finally ready to do another classpath import, and near the last
>>> minute I realized that the import may temporarily break the build, due
>>> to an unfortunate interaction between the classpath Makefile and the
>>> way cvs import works. FWIW I'd prefer to continue using cvs import
>>> since it does seem to help the process a little.
>
> Dave> Is this anything that could be fixed with a "cvs admin -b"
> Dave> immediately after the import?
>
> I've never used that, but based on the manual, I don't think so.
> The problem is that files that are new on the vendor branch will show
> up on HEAD immediately, and classpath will try to build them.
>
> Tom
Ah, that was part 2) of the problem, the bit I had trouble with was the
way it kind-of auto-merges across any unchanged files by setting their
default branch to vendor branch instead of trunk.
What version of CVS are you using, and does it speak the "-X" option (new
in 1.12.x)?
http://ximbiot.com/cvs/manual/cvs-1.12.12/cvs_16.html#SEC155
cheers,
DaveK
--
Can't think of a witty .sigline today....