PHP ports/packages framework is seriously flawed

Valéry valery at
Fri Jan 14 06:22:39 PST 2005

i'm not from FreeBSD, but if i can advise you :
php is *very scalable*, and before having all
options you want, you must build it 5 or 6 times.
I'm using 4.3.4, and it was compiled not from
the BSD ports, but from the sources.
The 1st reason is that - i think - a port cannot show
you every configuration you want, specially with
php ; there's a lot of '3rd part software' with
php. The second one is that compiling php in
this way is not difficult, php is well done,
and well documented, and you'll get
exactly what you expect from php (eg GD, XML,
XSL, CLI or CGI, ...).
More, you can patch your php without waiting
a new port, and this is important for security.
In my point of view, i think that with a
solution like php, you must know everithing
about it, specially at the build time, this
is very important if you want to be accurate,
and know why you get an error using a
functionnality ; you'll win time.
Well, try to compile it yourself, and see
what you want.
i hope this help you,

Maxim Sobolev wrote:

> Hi guys,
> Maybe I am missing something obvious, but as long as I can see, the 
> whole PHP framework is currently severely flawed. Specifically I am 
> talking about www/mod_php4 port/package. Current system doesn't allow 
> any PHP extensions to be installed for it, at the same time when 
> building mod_php4 it explicitly disables all possible extensions, so 
> that resulting module is nearly useless since it lacks even essential 
> functions and it's impossible to install them later on.
> Perhaps FreeBSD PHP maintainers should take a closer look on how this 
> problem is addressed in major linux distros.
> Regards,
> Maxim
> _______________________________________________
> freebsd-ports at mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at"

More information about the freebsd-ports mailing list