rahul wrote: > > Even mod_perl that we bundle today, has the same issues.
Yes that has issues... it's been around a long time so this particular case isn't the best place to solve it.. > | So, for the three in this case, do they have such dependencies that > | warrant individual packaging? What are the dependencies for each one? > > Except for PCRE for mod_security, there aren't any other dependencies. Ok.. good to know. > | For the ones which don't add any special dependencies, I'd rather see > | them in SUNWapch22u along with the rest of the mostly self-contained > | modules. > > I had mentioned my concern in the earlier mail. I would prefer the other > modules (svn/perl) that are not part of main apache source also to be kept > in different packages. Hopefully others in the community have some opinions.. I've not managed to convince myself absolutely one way or the other. Either way works. If they had significant dependencies, pulling in packages that not everyone wants, then they'd have to be separate packages. These don't meet that criteria so inside SUNWapch22u is fine and won't cause annoyance. But separate packages for optional modules has its elegance as well. I see debian has tons of "libapache-mod-*" pkgs. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
