I haven't investigated all of the possible issues, so just mention here what I see at the moment (a chaotic and incomplete list):
1. For apache 2.4 most of the changes mentioned by https://httpd.apache.org/docs/2.4/upgrading.html are not covered by puppet, for example: - some modules are removed from apache 2.4 (for example mod_authz_defaultis on the list of default modules in puppetlabs/apache), - few modules changed their names in 2.4 (e.g. cache_disk instead of disk_cache), - syntax for authorization and access control has changed in apache 2.4 (e.g. "Require" instead of old "Allow/Deny") - should be reflected in apache configs generated by puppet, - other configuration changes (for example SSLMutex option has been removed - currently this setting is generated by puppet module), 2. For FreeBSD: - FreeBSD has rather specific packaging system (ports), for example package names are in form 'www/apache24' (for apache2 v 2.4), - most modules are available as (compile) options of bigger packages, for example mod_php5 compiles and installs together with lang/php5 port (and some flags need to be enabled, when compiling the www/php5 port), - specific directory layout (ports are installed under /usr/local, apache modules are under /usr/local/libexec/apacheXY, etc.), - other differences, for example root's main group name is 'wheel' whereas on most Linux'es it's 'root', For apache, I think, the best option would be to develop some way of multiversion support (depending of what is installed on a given system). For FreeBSD, the most dificult part, I think, is to implement what is now driven by $mod_packages (manifests/params.pp) for other OSes. It seems that for FreeBSD/ports there is currently no support for setting compilation options in puppet. In most cases, the only way to have some apache module installed is to (re)compile appropriate package after altering its build options. Majority of modules are available as options to ww/apacheXY port for example. W dniu wtorek, 23 lipca 2013 19:11:11 UTC+2 użytkownik Aaron Stone napisał: > > What doesn't work as the code currently stands and needs to be changed? > Just to understand the scope of work that you might need to do to port the > module. > > > On Tue, Jul 23, 2013 at 7:29 AM, Pawel Tomulik > <[email protected]<javascript:> > > wrote: > >> Hi, >> >> I'm trying to adapt puppetlabs/apache module to work with apache 2.4 on >> FreeBSD. I've already created a branch of puppetlabs/apache and started >> looking through the code, but I'm curious if there is no similar job >> already done (or started). Do you know anyone has already done this, or >> maybe have you heard about similar efforts? >> >> Best regards! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/puppet-dev. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
