Re: checking in links to source control

[Edward Peschko]

On Wed, Sep 12, 2001 at 11:41:34AM -0400, Jeff King wrote:
> > From: Edward Peschko [mailto:address@hidden
> > Sent: Monday, September 10, 2001 4:34 PM
> > To: Jeff King
> > Cc: address@hidden
> > Subject: Re: checking in links to source control
> >
> >
> >
> > I want developers to see - locally - all of the perl libraries
> > cross project.
> > When I do a release, I want people to do a simple 'cvs checkout'
> > to get the
> > entire project, and have it *work on the spot*. I want them to be able to
> > 'cd lib' into any project and get to the point where the
> > libraries are stored.
> 
> And controlling the perl libraries in a separate module from your other
> projects will accomplish just that. Is having to do "cvs checkout project"
> really more difficult and complicated than "cvs checkout project", "cvs
> checkout lib"? Is "cd ..\lib" more difficult than "cd lib"?

Like I said, I'm already planning on doing this. But I want a standard way of
getting to those libraries, no matter where in the project I am.

Suppose the libraries are two steps up from a project, in '../../lib'? Or 
three steps up? I can't standardize on any 'use lib' statement then, I'd have
to resort to $FindBin::bin trickery (as was stated earlier).

Or perhaps I want to only link to the libraries actually being *used* in a 
project, rather than everything, so I can tell at a glance the dependencies a 
given project has without wading through source code?

Or perhaps I want to have several links to the same *script*, but in different 
directories, my process is data driven rather than script driven and it makes
sense for the script to live with several different groups of data.. 

Who knows? In any case, links are there for a purpose - they are useful, and
ubiquitious (at least on unix systems). And I'd like the ability to put them
in source control.

Ed