Date: Tue, 27 May 2003 11:35:04 -0000 From: Jens Rehsack <rehsack@liwing.de> To: Alex Dupre <sysadmin@alexdupre.com> Cc: MichaelSharp <ms@probsd.org> Subject: Re: mod_php ( new ) Message-ID: <3ED34D64.2030907@liwing.de> References: <4220.192.168.1.4.1053863593.squirrel@probsd.org> < 71646554.1053871112@cmantatzi.in.t-online.fr> < 3ED0B126.2060206@liwing.de> <85414385074.20030527122227@alexdupre.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/27/2003 12:22 PM, Alex Dupre wrote: > Sunday, May 25, 2003, 2:03:50 PM, you wrote: > > Jl> I hope, Alex can fix the problems so that my pr can closed without > Jl> getting committed, but (as I said) I don't know and it may be a chance > Jl> to use 4.3.2 til it's fixed. > > The problem is not in my ports, but in others depending on mod_php4, That's not completely true. That's the same reason as it is for 16 bit real-mode on Pentium4 processors :-) > which should be fixed. Now if a port requires pear, or apache mod, or > php cli, it depends *always* on mod_php4. Wrong! After the re-commit of I maintain devel/php-dbg, but I need a working php port to fix the problem devel/php-dbg has with new php4 port. > 4.3.2 (hopefully the release and not rc4) every port should depend on > the correct php port (lang/php4-cli, lang/php4, www/mod_php4, > www/php4-cgi, devel/pear). Since this may be a tedious task and some > ports work with different php sapi, I create an include makefile to > simplify it (PR 52674). I've recognized it. Looks to be great work. A possible solution may be, creating a new slave port for mod_php4, let's say www/php4_module and let it conflict with www/mod_php4 (as well as lang/php4 and lang/php4-cli). Than each port which depends on mod_php4 could be checked separately without requiring a huge commit for all ports. Maybe it's a good point to start. Regards, Jens
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ED34D64.2030907>