Re: How to make update -d ignore a top-level directory?
Shankar Unni writes: * Be able to sit at the root of my work area (where I did the cvs checkout), and be able to do a simple cvs update -d. * Have the cvs update -d fetch everything except a single top-level directory I don't want. Unfortunately, that is not possible with the current design of CVS. There is no way for update to distinguish between a newly-added directory and an old directory that you explicitly chose not to check out in the first place. -Larry Jones You just can't ever be too careful. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: How to make update -d ignore a top-level directory?
Larry Jones writes: Unfortunately, that is not possible with the current design of CVS. That's what I figured. Oh well, time for a module move. Actually, what I really need to do is to reorganize the top-level modules - the mistake was that our original core code was not neatly checked in in the form of a module; instead, all the top-level directories under our source tree (src, lib, doc) were checked in as modules. Sigh! Thanks all, -- Shankar. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
How to make update -d ignore a top-level directory?
In short, this is what I'd like: * Be able to sit at the root of my work area (where I did the cvs checkout), and be able to do a simple cvs update -d. * Have the cvs update -d fetch everything except a single top-level directory I don't want. First attempt: I defined the module as tms -a src lib doc utl(everything except CVSROOT and nms) This works fine, except that the directory where these four end up does not contain a CVS directory, so I cannot sit in that directory and issue any CVS commands (except by separately setting a CVSROOT environment variable or using the -d option). Second attempt: I defined it as tms -a . !nms This works great for *checkout*, and creates a CVS directory with Entries, etc. The problem is that if I then issue a cvs update -d in that directory, it gets that pesky nms directory (50 MB of useless stuff). How can I achieve what I want: to be able to: * not have to set CVSROOT in the environment. * Be able to issue an update -d from the root of my work area, and * not get that junk directory? Is there a way? I'm trying to avoid having to do a radical nms-ectomy (:-/) on my repository.. Thx, -- Shankar. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: How to make update -d ignore a top-level directory?
On Tue, 2002-11-19 at 10:02, Shankar Unni wrote: How can I achieve what I want: to be able to: * not have to set CVSROOT in the environment. * Be able to issue an update -d from the root of my work area, and * not get that junk directory? Is there a way? I'm trying to avoid having to do a radical nms-ectomy (:-/) on my repository.. In CVSROOT in your repository there's a configuration option in one of the files - I think it's called config - that is 'TopLevelDir'. Set it to yes, and the directory you're in when you run cvs checkout gets a CVS subdirectory. I believe that will do what you want. Jenn V. -- Do you ever wonder if there's a whole section of geek culture you miss out on by being a geek? - Dancer. [EMAIL PROTECTED] http://anthill.echidna.id.au/~jenn/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
