RE: Re: VSS File Sharing

--On Wednesday, November 15, 2006 11:28 PM +0000 Steve O'Hara
<sohara@pivotal-solutions.co.uk> wrote:

> modules in our projects that provide stable and well tested libraries.
> An engineer here starts a new project by firstly going to VSS and drags
> together all the files they intend to use as a framework. It does mean
> that you get some bloat, but it's worth the cost.

The "fold it all into a bowl and stir" model of development. This should
introduce no more or less bloat than keeping the modules in a separate
library. But I can't see how it makes working with the modules easier.

I'm introducing a new vendor library into some old code moved from VSS to
SVN. That library is going into its own directory, not getting dumped into
the project directory as has been done by other developers in the past.
It's a separate subsystem, and it should be organized that way.

Dumping all your modules into one directory is like dumping all your source
into one big text file. Those with primitive single-file editors may like
the latter, but I find huge source files clumsy, and I find huge
directories full of unrelated modules equally clumsy.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 16 03:13:46 2006