Doug Lee <[EMAIL PROTECTED]> wrote: > Now for why...
> I write scripts for a screen-reading program called JAWS For Windows > (JAWS stands for Job Access With Speech). JAWS scripts must all exist > and run in a specific directory, say c:\jaws510\settings\enu. JAWS > scripts are named after the applications to which they apply; thus, a > script for WordPad will be named WordPad.jss (source code; the > compiled version is WordPad.jsb, and there are other associated > WordPad.* files as well). Every script for every application that > needs special handling goes in the same directory. This is how it > comes to pass that I often have multiple simultaneous projects in the > same directory with no overlapping file names. I see. Well, allow me to pontificate a little. Your files are scripts and require no compilation, so you make the common mistake of confusing the *source tree* of your project (your scripts) with the *installed version* of your project (your scripts in jaws510\settings\enu with all their other script friends). The source tree goes into CVS, the installed copy doesn't. You should be doing a "make install" or some such to install your files... ... except that it sucks, because you can't even *test* your scripts without installing them. Which is why the above qualifies as pontification. Bottom line: JAWS is not nice, and there is nothing you can do about it. Or does JAWS understand shell links (aka Windows shortcuts) ? If yes, you could plant shortcuts from the installation directory to your CVS sandbox. Is there a tool to plant shortcuts programmatically? One other thing: are you the only one involved that uses CVS? if so I guess your approach is okay, but your initial post said something about telling everyone else to stop committing to the trunk while you were away. That negates the "C" in CVS, which is a shame. -- pa at panix dot com _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
