Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
Xin LI ha scritto: I usually use portupgrade -fr lang/php5, but I think it may worthy to just bump PORTREVISION across PHP upgrade. Every php extension (optimizer, pecl, accelerator and so on) needs to be recompiled after updating base PHP. I cannot bump all ports when php4 or php5 is updated, be serious :-) Recursively updating all the extensions is the right thing you have to do. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
On Wed, 06 Jun 2007 09:33:35 +0200 Alex Dupre [EMAIL PROTECTED] wrote: Xin LI ha scritto: I usually use portupgrade -fr lang/php5, but I think it may worthy to just bump PORTREVISION across PHP upgrade. Every php extension (optimizer, pecl, accelerator and so on) needs to be recompiled after updating base PHP. I cannot bump all ports when php4 or php5 is updated, be serious :-) Why ? We did this in the past for enough ports, we do it for claws-mail-*, etc. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect signature.asc Description: PGP signature
Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
Quoting Alex Dupre [EMAIL PROTECTED] (from Wed, 06 Jun 2007 14:30:38 +0200): Ion-Mihai Tetcu ha scritto: Why ? We did this in the past for enough ports, we do it for claws-mail-*, etc. Do we bump every p5-* port when we update perl? No, but you are supposed to update them. Here is even more complex: if I update php4, why should php5 users update their extensions? There is no reason. And only a minimal part of the extensions will effectively require an update, so it's simpler to deal with them only when a breakage occurs. As a data point: the claws-mail plugins are bumped because the plugins don't startup when they are not recompiled. They contain the claws mail version number and bail out if the compiled in one is not equal to the version number of the currently running claws-mail. So anyone using plugins has to update them on each claws-mail update. The portrevision is bumped to trigger this explicitly. This way we also get suitable packages (but I don't remember if this would be the case anyway). My advise would be to do the same with those ports, which show similar behavior. Regarding php and eaccelerator: I always recompile eaccelerator by hand when I update php, so I would not mind if the revision of eaccelerator would be incremented on each version bump of php (disclaimer, I didn't follow this discussion and stumbled upon this specific mail only by accident). Bye, Alexander. -- Cthulhu for President! (If you're tired of choosing the lesser of two evils.) http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
suggestion: force removal and reinstallation of eaccelerator on php upgrade
Reason: when you upgrade php, for example for 5.2.2 to 5.2.3, and forget to uninstall and reinstall eaccelerator, it will break web services (if php is active as module) and php -i will look like: [EMAIL PROTECTED] ~]$ php -i [EMAIL PROTECTED] ~]$ I presume it's possible to define such a behaviour ? eAccelerator has to be compiled on each php version change. Regards from Zürich, Olivier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
在 2007-06-05二的 17:48 +0200，Olivier Mueller写道： Reason: when you upgrade php, for example for 5.2.2 to 5.2.3, and forget to uninstall and reinstall eaccelerator, it will break web services (if php is active as module) and php -i will look like: [EMAIL PROTECTED] ~]$ php -i [EMAIL PROTECTED] ~]$ I presume it's possible to define such a behaviour ? eAccelerator has to be compiled on each php version change. I usually use portupgrade -fr lang/php5, but I think it may worthy to just bump PORTREVISION across PHP upgrade. Cheers, -- Xin LI [EMAIL PROTECTED]http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: 这是信件的数 字签名部分
