Prev: [patch] fix config-recursive
Next: Port version difficulties (maybe one for the Python crowd)
From: Carsten Wiedmann on 7 Dec 2009 12:02
Hi Alex,

>> So you don't plan to leave 5.2.x version in ports for people who need to
>> maintain servers in production with many clients and many 'old' web
>> applications?
>
> Like we don't have ports for php 5.0 and 5.1, I'll not maintain ports
> for 5.2 when the switchover will take place.

I don't think you can do that. 5.2 is a separate branch to 5.3 and still
maintained. And for normal customers it's not such easy as you can read in
"migration53.incompatible.php". In our own project (XAMPP), there are a lot
questions from customers about how the replace the bundled PHP5.3 with PHP5.2.

Just some points:
- Many common webapps are not working with 5.3 at this time, e.g. Drupal6.
- An other example may be Joomla. I know, 1.5.15 (core) should be compatible
with PHP5.3, but that's not completely true. Especially not for Joomla add-ons.
- And a lot of others have problems with 5.3. (and not all FreeBSD users are
full time admins ;-) )

- there are extensions which are not working with PHP5.3
- there are extensions which are more exclusive in PHP5.3 (the PECL versions
are not the same or unmaintained (e.g. sqlite3 / fileinfo)).

On the other side we need PHP5.3, because if someone need the new functions,
or is just an developer of an webapp. (if these have not gone in the
meantime to another OS).

And the ZendOptimizer is not a loss. We have APC or eAccelerator. So only
the encryption function is left. But this is still working with 5.2. And of
course, there is also no ZendOptimizer for PHP5.3 for any other OS (which is
officially support from Zend). So I guess "some" have switched.


Now the last questions:
You still need tests with the PHP5.2 patch and feedback? Or something else?

Regards,
Carsten

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Alex Keda on 7 Dec 2009 12:53
Miroslav Lachman пишет:
> Seriously - if ports team is willing to have "legacy" versions in ports,
> we need to discuss some rules for this work. Not just for PHP, but more
> general. In which conditions we need/allow them, the naming conventions
> (some ports already have more versions but names are not consistent,
> some ports are using -dev, -devel, -current [3 different sufixes for the
> development branch], Perl always uses p5- prefix, Python have py25-,
> py26- etc.)
> So is it better to renumber the legacy (forked) version to
> php52-ext_name-5.2.12 leaving php5- line for 5.3 version or do it like
> Python (py25, py26): php52- and php53-.
It's good idea.
But, it may be very hard.
I very small know about port system (but, I maintain two or three ports
=)), but can small help - some test, or "hands" operations (rename, & etc)
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 | 
Pages: 1
Prev: [patch] fix config-recursive
Next: Port version difficulties (maybe one for the Python crowd)