Because then other people could benefit from the work you did instead of repeating it. Compiling PHP is not a trivial task, especially if one wants more than bare functionality. It could have saved someone lots of work. “Because I’ve used MySQL for ages, and I don’t relish migrating a database in the middle of this already huge migration. It’s something I’ve thought about for a while but I haven’t had any issues with MySQL myself, so it hasn’t been pressing for me.”

At least you considered the possibilities, which is already a lot more than most people would do. That’s certainly commendable. I can sure understand how having a legacy DB and switching over would be a dilemma.

Did you build PHP using Sun Studio 12 compilers?

No, Sun Studio 11 - because I had it handy from ON builds.

Did you use Sun Studio optimizations?

Yup

Does your PHP have support for SNMP, and most importantly, for Oracle?

Nope, why would I need those? I don’t use SNMP or Oracle, so why would I build those in?

It seems like such a shame to use a half-baked, wannabe RDBMS like MySQL when Solaris ships with PostgreSQL, a real, high quality RDBMS.

Because I’ve used MySQL for ages, and I don’t relish migrating a database in the middle of this already huge migration. It’s something I’ve thought about for a while but I haven’t had any issues with MySQL myself, so it hasn’t been pressing for me.

Did you build PHP using Sun Studio 12 compilers?

Did you use Sun Studio optimizations?

Does your PHP have support for SNMP, and most importantly, for Oracle? “Yes, I realise that packages for these already exist on Blastwave and elsewhere, but I want ones that leverage the Apache2, MySQL, and OpenSSL that Solaris already ships with.”

It seems like such a shame to use a half-baked, wannabe RDBMS like MySQL when Solaris ships with PostgreSQL, a real, high quality RDBMS.

Anyway, good progress on the grommit buildout. When you’re done, be sure to document the setup before you let us messy users into the nice clean box…..