Re^2: non-CPAN module distributions

You have nothing to gain by making separate installations unless you intend to use these modules in separate places.

Hmm. I sometimes develop in this way. You do get some useful things from this model:

You can easily separate the test scripts that apply to this particular module from those that apply to another. This allows you to easily run only the relevant tests when testing a module. This can save time and make TDD considerably more pleasant.
People can work on modules independently from each other.
It can give you a nice clear separation of unit tests (distributed with module directory) and acceptance tests (distributed with application as a whole).
Allows you to easily release module updates rather than application updates as appropriate.

There are certainly other ways of getting these benefits, but the CPAN-ish structure gets you a lot without any effort.

Comment on Re^2: non-CPAN module distributions

Replies are listed 'Best First'.
Re: Re^2: non-CPAN module distributions by perrin (Chancellor) on Sep 16, 2003 at 21:59 UTC
I think you can do all of these things just by making separate test scripts for each module and only running the one that pertains to the module you're working on. That's what I'm doing now.	[reply]
Re^4: non-CPAN module distributions by adrianh (Chancellor) on Sep 16, 2003 at 22:29 UTC
Having a single test script per module is not always practical. Also I find having people work independently is harder if you keep everything bundled together. With separate distributions you can check individual modules in and out, only update single modules, avoid name clashes with test scripts from other modules, document prerequisites on a module-by-module basis, etc. There are certainly other ways of getting the same sort of functionality - but I don't see that having multiple module directories has any major disadvantages.	[reply]