On May 23, 2012, at 19:28, Bradley Giesbrecht wrote:
>
> On May 23, 2012, at 4:05 PM, Ryan Schmidt wrote:
>
>>
>> On May 23, 2012, at 16:39, Bradley Giesbrecht wrote:
>>
>>> What is the argument for apache2 to continue violating mtree?
>>
>> The only one I can think of is that tons of other ports currently assume
>> that's the layout. Thus changing the apache2 layout requires changing tons
>> of ports in unison.
>
> Is this not accurate?
> port file depends:apache2 or variant:apache | sort -u | wc -l
> 44
Hmm, I had thought there would be more than that.
>> If we instead made a new apache24 port we would be free to give it any
>> layout we wanted, and then over time adapt all the other ports to depend on
>> apache24 instead of apache2. It would still be an unpleasant time for users
>> of those ports until all of them are converted and apache2 is deprecated.
>
> Might not be that big of a project.
> $ echo $MP_SVNDPORTS
> /opt/local/var/macports/sources/svn.macports.org/trunk/dports
> $ find $MP_SVNDPORTS -maxdepth 3 -name Portfile -exec echo {} \; -exec grep
> -E "/apache2" {} \; | grep -B1 -v /Portfile
>
> Some ports would become simpler with apxs in PATH.
>
> /opt/local/var/macports/sources/svn.macports.org/trunk/dports/www/mod_ssi_func/Portfile
> ...
> build {
> foreach mod ${mods} {
> system "cd ${worksrcpath}/${mod} && \
> make APXS=${prefix}/apache20/bin/apxs"
> }
> }
Note that mod_ssi_func isn't a good example because it specifically requires
apache 2.0; it does not work with 2.2 or later, as I understand it.
> Removing mtree violations is a worthy topic.
Agreed!
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
