June 2009

PHP updated to 5.3.0

The people from PHP have released a new version. I’ve downloaded it right away and installed and tested it on all my test machines and haven’t found any problem yet. This release is a major improvement in the 5.X series, which includes a large number of new features and bug fixes.

  • Support for namespaces
  • Late static binding
  • Lambda Functions and Closures
  • Syntax additions: NOWDOC, ternary short cut “?:” and jump label (limited goto), __callStatic()
  • Under the hood performance improvements
  • Optional garbage collection for cyclic references
  • Optional mysqlnd PHP native replacement for libmysql
  • Improved Windows support including VC9 and experimental X64 binaries as well as portability to other supported platforms
  • More consistent float rounding
  • Deprecation notices are now handled via E_DEPRECATED (part of E_ALL) instead of the E_STRICT error level
  • Several enhancements to enable more flexiblity in php.ini (and ini parsing in general)
  • New bundled extensions: ext/phar, ext/intl, ext/fileinfo, ext/sqlite3, ext/enchant
  • Over 140 bug fixes and improvements to PHP, in particular to: ext/openssl, ext/spl and ext/date

This release also drops several extensions and unifies the usage of internal APIs. Users should be aware of the following known backwards compatibility breaks:

  • Parameter parsing API unification will cause some functions to behave more or less strict when it comes to type juggling
  • Removed the following extensions: ext/mhash (see ext/hash), ext/msql, ext/pspell (see ext/enchant), ext/sybase (see ext/sybase_ct)
  • Moved the following extensions to PECL: ext/ming, ext/fbsql, ext/ncurses, ext/fdf
  • Removed zend.ze1_compatibility_mode

For users upgrading from PHP 5.2 there is a migration guide available here, detailing the changes between those releases and PHP 5.3.0.

For a full list of changes in PHP 5.3.0, see the ChangeLog.

For instructions on how to upgrade PHP please read: Upgrading PHP.

Courier updates

Sam Varshavchik has been busy again checking everything against the new version of GCC and fixing a minor bug. He has done this for most of the Courier software stack. The ones that concern us are:

Courier-Auth was updated to 0.62.4

  • Various compilation fixes for gcc 4.4 and libtool 2.2

Courier-IMAP was updated to 4.5.1

  • Various compilation fixes for gcc 4.4
  • fetch.c (open_cached_fp): If the message file cannot be opened,
    create a dummy message in its place.

Courier Maildrop was updated to 2.2.0

Please do not use this version as it will not work, please download version 2.0.4. I’m not spending more time on this as of the switch to dovecot later this week.

  • GCC 4.4 fixes

Updating should be easy, just follow the install instructions as usual.

XCode 3.1.3 released

Just to inform you all as I missed it myself. Apple have released a new version of XCode. It’s not mandatory to upgrade but I will do it myself and all instructions etc. will be based on this version although I don’t expect any issues if you keep using the previous version.

You can download it from developer.apple.com. If you don’t have an account yet, just register. It’s free if you just want to download XCode and the related information.

What’s new in XCode 3.1.3:

  • SDK support for targeting non-Mac OS X platforms, including iPhone OS SDK.
  • GCC 4.2 & LLVM GCC 4.2 optional compilers for use with Mac OS X 10.5 SDK
  • Updated assistants to create new projects, targets, and source ?les
  • Toolbar uses a single popup to choose platform, target, and debug/release
  • Integrated SCM support now works with Subversion 1.5

Hawk Wings is back!

Yes, Hawk Wings the blog for everything related to Email, Todos and more is back. Tim Gaden has started to blog again after being more than a year off-line. His blog has been (and will be) a valuable source of information for people wanting to get the most out of their email (and related) programs on their Mac.

Finally solved SQLGrey and KeepAlive problem

You could call it brainwave or an enlightened moment after SQLGrey died on my server again. Which I usually notice after not having received any mail for a day. After trying so many times to get this thing solved properly I finally got it. I can really feel stupid now that I know the solution was so simple.

I just had to remove the ‘-d’ option from the startup command line. This option is used to start SQLGrey in daemon mode. SQLGrey will spawn a new process which will be kept running and the process which you started will end. This was the reason when I first tried to use KeepAlive that launchd would try to start a new SQLGrey process every 10 seconds because the orinal process had ended.

This now works on Leopard, still need to test this on Tiger. I’m currently rebuilding Tiger on my old G4 mini who’s harddisk had died. Currently using an external firewire drive as I still need to buy a new internal disk. The G4 is still needed as it is my only PowerPC based Mac and I swant to test everything on Tiger or Leopard on this CPU as I know many of you still use an old PowerPC based Mac to run as a server.

The instructions have been updated to reflect the new found knowledge. Sorry this took so long to find out.

Next Page »