apache2 path layout

[bchesneau@…]

I put a little modification apache2 layout to put all conf files on $prefix/apache2/conf . I also create an Opendarwin layout. I do the same for apache 1. I think this is more easy to maintain apache modules and this the way used mainly by other mainteners.

The layout is :

prefix: /opt/local/apache2 exec_prefix: ${prefix} bindir: ${exec_prefix}/bin sbindir: ${exec_prefix}/bin libdir: ${exec_prefix}/lib libexecdir: ${exec_prefix}/modules mandir: ${prefix}/man sysconfdir: ${prefix}/conf datadir: ${prefix} installbuilddir: ${datadir}/build errordir: ${datadir}/error iconsdir: ${datadir}/icons htdocsdir: ${datadir}/htdocs manualdir: ${datadir}/manual cgidir: ${datadir}/cgi-bin includedir: ${prefix}/include localstatedir: ${prefix} runtimedir: ${localstatedir}/logs logfiledir: ${localstatedir}/logs proxycachedir: ${localstatedir}/proxy

find path of confog.layout and apache 2 portfile patch

[bchesneau@…]

patch cvs portfile

[bchesneau@…]

patch-config.layout

[bchesneau@…]

Patch Portfile in cvs

[bchesneau@…]

files/patch-config.layout

[bchesneau@…]

files/update-apachemodules.pl

[bchesneau@…]

err.

[fkr@…]

what is the status on this? -fkr

[bchesneau@…]

No news from jasonc or michaelm, yet. I think that apache or apache2 should be installed in ${prefix} and not in ${prefix}/${name} for apache2 and ${prefix}/${name}-${version} for apache . This the way choosen by freebsd or other packagers. Like with mysql, I don't see the need to have both apache installed. And since darwinports don't manage installation of the same package with differents variants, we could not install a module with darwinports for apache and apache2 (for example php4 cant' be installed for apache and apache2...). For instance, I updated php4 to install with apache or apache2 currently in cvs.

But I think that installation layout should be discuted here, it would be usefull in the future to add more apache modules in darwinports.

About update-modules,sh, I think now that a better way could be a config target in darwinports to manage configuration process after installation. Would mail darwinports ml today to ask to others.

[fkr@…]

jason, could you comment on this, please -fkr

[jcorley1@…]

I don't like this setup. First, the apachemodules.pl is redundant given the functionality provided by apxs. Secondly, the patch would make apache 1.x and apache 2.x conflicting, which I feel is a bad thing. They should be able to coexist, imho. So the way to go about this is a) do nothing or b) rename all apache 2.x binaries and directories named foo as foo2. I'm open to other suggestions, but right now I think a) is the way I'm leaning, unless someone can present something to me that doesn't make b) absolutely hideous. So in summary, I'm rejecting this because it doesn't play nice with apache. Jason

[bchesneau@…]

Mmm, about apachemodule you're right, it was just a try to have an easy installation of modules with their configuration files that could be included in apache. But about apache2, why having apache and apache2 installed on the same machine ? Modules can't be installed with both like php4. And dport don't manage installation of the same dport with different variant. If you want apache2 that work with apache why not create an apache variant to have apache layout (install in ${prefix}/apache2) like the apache dport ? Btw FreeBSD layout don't exist in apache2 you should add it to config.layout file If you want it.

[jcorley1@…]

FreeBSD layout was added in the latest version of apache2. Since I think people want apache and apache2 on the same machine I'm resolving this bug.