Re: checking in links to source control

[Edward Peschko]

> Of course you can.  This is trivial.  Simply push the starting point for the 
> libs 
> 
> onto @INC and then merrliy go about issuing your use statements.  For example:
> 
> 
> push (@INC, "/top/dir1/dir2/perlLibs/");

... which of course assumes that everybody has their cvs archives checked out
in the same absolute path.  been there, done that.

hmm.. maybe I'm not making myself clear enough. All I want is for CVS to support
any type of filesystem object. dirs, files, links, resource forks, aliases,
shortcuts, special character files, etc. The point about the environment
is secondary - all I'm saying is that it is my environment, I should have
the freedom to set it up the way I'd like and not have the tool get in the
way.

So far no one has disagreed. So is everyone in agreement with this basic goal? 

Ed