Rodney> Ok, I checked it out as -r Carbon_post_21_5_15_merge and Rodney> it refers to Carbon-specific instructions in Rodney> macintosh/INSTALL, however, I don't find that file in that Rodney> directory (or anywhere else that I could think of). Am I Rodney> doing something wrong? Nope, usual CVS bogosity, I forgot to add so it never got committed. It's there now. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.

Rodney> Ok, I checked it out as -r Carbon_post_21_5_15_merge and Rodney> It might be there, but I'm having trouble getting it out Rodney> of cvs. I tried both a checkout with the tag and a cvs Rodney> update, but I don't see the file. Oops. I didn't notice which tag you used; that tag is a fixed tag intended to record the _exact_ changes made to the Carbon branch in lieu of a patch, and will never be updated. (In principle; in this case I probably will---no harm will be done---but don't depend on it.) Just use the branch tag: cvs update -r Carbon in the workspace to get the tip of the Carbon branch. When active development resumes (ie, we start breaking things that already work) in Carbon, I'll implement a Carbon-latest-beta tag that refers to the latest code that I know at least builds. But for now, things are quiet, so just follow the tip of the branch. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.