From: Jorge B. G. <yor...@gm...> - 2007-09-27 18:45:11
|
O M=E9rcores 19 Setembro 2007 10:42, Alberto Garcia escribiu: > O M=E9rcores 19/09/2007 =E1s 10:38, Xabier Rodriguez Calvar dic=EDa... > > > > The problem comes with bmodules. There are 10 modules, most with > > > 3 versions (common, client and server), and adding the -dev, -doc > > > and -dbg packages, there will be near 100 packages. It can be > > > really hard to work with that amount of packages. Not only for > > > creating them, but for using them. > > Indeed. I wouldn't create 100 packages of modules. =46inally I followed an intermediate solution: instead of put each module i= n its=20 package, I splitted the modules in two categories: basic and extra. The basic modules are those that will be in every fisterra application for= =20 sure (auth, calendar, document, payment and tax) and extra are the "optiona= l"=20 packages (replication, uddi and migration). Each group has its=20 lib, -dbg, -doc and -dev package. I think this is a good solution, because the modules in the basic group dep= end=20 on each other and they are used almost always together, and at the same tim= e=20 we give more install options than all or nothing. Anyway, if a particular module grows and it would be better in its own=20 package, it's better to split that package when that happens and not now. |