Adam Kennedy said:
While I'm thinking about it, has anyone talked to Red Hat or the Debian people to see how the separate distribution of identically named module will work within all of the distro's various packaging systems?
Doesn't seem like a problem to me since a) they just ship the mod_perl that goes with the apache version they choose to ship and b) their package systems work fine with anything that doesn't have overlapping files, and the current mp2 plan has no overlapping files.
what about manpages? Those do overlap. Or may be they don't install those? In any case, this is not a problem, since any system that has more than one generation, which doesn't change the API (take BerkleyDB for example, but it's true for 99.9% of C projects) can have only one set of manpages.
I think we should advise packagers (this is from my summary-in-progress):
=item * Distributors
Distributors should mark the different generations of mod_perl as conflicting, so only one version can be installed using the binary package. Users requiring more than one installation should do a manual install.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
