rahul wrote: > > | Which leaves mod_security, does it have any interesting dependencies? > > It just has pcre which we already have as part of the SXDE.
What I'm looking at is not whether it's available (well, it has to be available for the build to work so it's a given!) but whether it is a dependency that pulls in unwarranted (for some users) packages. For the SXDE distro that's largely irrelevant since it is one big DVD that throws everything onto disk anyway. But later with IPS when I get to pick only packages I really want, it'll be important to avoid bringing in large chunks of functionality not everyone might want (e.g. installing apache shouldn't require installing, say, postgres, because not everyone who wants apache always wants postgres). For smaller common libs like pcre it doesn't seem like a big deal even if I don't want pcre. Admittedly the line is a bit fuzzy here.. > There is a caveat involved in adding all to SUNWapch22u, If we plan > to allow users to compile the sources directly in their machines > (like FreeBSD ports) then a breakage in any of the dependent sources > can break the entire source build. Thus if there is a build break > in mod_jk, it will break apache22 too. While this is not a concern > right now, I think it should be considered because of the future > impact. Yes and if ruby build breaks why should postgres nighly build be busted (not to pick on ruby ;-)... you're right, the current huge consolidation model doesn't really work and will crumble under its own weight soon. But... solving that will take a little longer. But for the above example, I wouldn't mind so much if things like apache and apache modules are closely coupled at built time since these are tightly related functionality anyway. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
