Yes... I suppose I have to. I was hoping Oracle would release a new 64-bit Lion-compatible version, but they have not.
The problem is that if I mark oracle-instantclient as 32-bit only on Lion and up, I have to do the same for everything that depends on oracle-instantclient (ocilib, php-oracle, qore-oracle-module, TOra) and everything that depends on those (fortunately none).
But then what will happen is a user will install php54-oracle. It will rebuild php54 and its dependencies universal. The user will run "php54 foo.php" and be surprised when oracle support is not available; the user will have to run "arch -i386 php54 foo.php" to get the 32-bit version of PHP. Or if the user wants to use this in a web server, the user will have to manually reinstall their web server SAPI (php54-apache2handler, php54-cgi, php54-fpm) with the universal variant, and then arrange to have it start in 32-bit mode. For php54-apache2handler, that means editing an "arch -i386" command into the apache2 start script—a change which will be lost anytime apache2 is upgraded, rebuilt or even just deactivated. It's basically a mess.
Users who actually use oracle-instantclient should please communicate to Oracle their need for a 64-bit compatible version of their software that works on Lion. And Mountain Lion. And while they're at it, fix the misconfiguration of their builds that requires users to set DYLD_LIBRARY_PATH.