| rahul wrote:
| > | > So, for the three in this case, do they have such dependencies that
| >
| > 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.
| >
| >
| Sorry, I am not able to understand as to what you mean by "build break
| in mod_jk" .
It is like this,
the user tries to build and install Apache22* packages, (A normal case -
users typically do 'make install' in the port) ,Since they depend on
mod_jk, mod_security2, mod_perl etc, these packages gets built _before_ the
Apache package gets installed. If by any chance these modules break
(say - user installed a Perl, that broke the compatibility with the perl
expected by mod_perl - it will break mod_perl for no fault of that
module.) Then the whole apache22* package will not get installed.
In general it is best to depend on as little things as possible to avoid
dependency hell.
rahul
--
1. e4 _
