RE: Alias module exclusion - subsequent update -d ignores exclusi ons

[Jim.Hyslop]

Matt Butt wrote:
> I've seen this mentioned in a few places as well but can't find any
> patches or hacks to fix it.
Nor should expect to see any, unless CVS gets a major rework in its approach
(see explanation below).

> If I have a tree such as
> 
>   MyModule/sourcefiles
>   MyModule/compiledfiles
> 
> And in CVSROOT/modules I have a line:
> 
>   MyModule_export -a !MyModule/sourcefiles MyModule
> 
> 
> 
> By executing:
> 
>   cvs checkout MyModule_export
> 
> I get just the MyModule/compiledfiles directory as expected.
> 
> 
> However, if I then do:
> 
>   cvs update -d
> 
> then MyModule/sourcefiles is retrieved from the repository.  It makes
> more sense to me to keep this directory excluded.  I know I can leave
> off "-d" but in the environment I'm using this (updating a live web
> server with the latest files from the CVS repository) this isn't
> acceptable.
The problem is, CVS does not keep track of which module your source comes
from. All it tracks is the directory in the repository. So, when you issue
the update command, CVS looks in your local CVS/Repository file and finds
that the current directory came from the directory MyModule in the
repository. CVS then looks at the MyModule directory in the repository,
discovers that the MyModule has a directory named sourcefiles and checks it
out for you, exactly as you told it to.

So, as you can see, CVS is working exactly as designed, and as desired.

I think some judicious restructuring of your modules would help. Right now,
you have module A, and module A-B. Change it so that you have module X, and
module X+Y (where X is the public stuff, and Y is the source).

-- 
Jim Hyslop 
Senior Software Designer 
Leitch Technology International Inc. (<http://www.leitch.com/>) 
Columnist, C/C++ Users Journal (<http://www.cuj.com/experts>) 



-- 
Jim Hyslop 
Senior Software Designer 
Leitch Technology International Inc. (<http://www.leitch.com/>) 
Columnist, C/C++ Users Journal (<http://www.cuj.com/experts>)