>
> CVS
>
> I presume that the CVS setup is going on somewhere in the
> background. When we have it, the directory structure will
> look something like this.
>
> P5EEx-Blue
> P5EEx-Blue/P5EEx
> P5EEx-Blue/P5EEx/Blue
>
> and all Perl modules for P5EEx-Blue (except P5EEx::Blue itself)
> will go in or below the P5EEx-Blue/P5EEx/Blue directory.
> The following other top level directories will be built.
>
> P5EEx-Black
> P5EEx-Orange
> P5EEx-Lime
> P5EEx-Green
> P5EEx-Beige
>
> This is to allow each P5EEx project to be independently
> releasable and CPAN-able if desired.
>
I would prefer a little deeper structure like:
P5EEx/Black
P5EEx/Orange
P5EEx/Lime
P5EEx/Green
P5EEx/Beige
and
P5EEx/Blue
P5EEx/Blue/P5EEx
P5EEx/Blue/P5EEx/Blue
so we don't get to many top level directories. On the top we can have P5EE
(in the future) and P5EEx. Haveing two separate directories hierachies for
both make things esaier to sort out.
The code Stephen has outlined for the Makefile.PL should go into a common
module P5EE::Build. This module would be caple of quering a common config to
set all the correct parameters for MakeMaker. It also would know about
directories and installed modules etc. For example I expect some module to
need mod_perl/Apache::Test for testing. P5EE::Build would tell them the
Apache build directories etc.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
