concrete5 add-ons install in FreeBSD

concrete5.org provides lots cool add-ons that can be installed by GUI in your concrete5 site.  The add-on is a archive zip file where it needs to be unzipped to your concrete5 web directory on the server.  If you try to install it by GUI with one click and your backend is running on FreeBSD, you going to see an install failed message without further details.  The root cause is that concrete5 hardcoded the path of unzip under /usr/bin/unzip

fix:
install unzip from FreeBSD ports, it will be located in /usr/loca/bin/unzip
cd /usr/ports/archivers/unzip
make ; make install ; make clean

make a symbolic link to it:
cd /usr/bin/
ln -s /usr/local/bin/unzip unzip

now you are done, enjoy one click install!

compile mysql 5.0.45 under freebsd 6.2

I had mysql4 running on my server, now I wanted to install mysql5 on the same box but also kept mysql4 co-exist. My choice was to compile mysql from source to a custom location. It is to be installed in: /opt/mysql-5.0.45/

After regular compilation and installation, FreeBSD complained about cannot find libmysqlclient_r.
From the INSTALL-SOURCE text file it indicated:
* If your client programs are using threads, you must compile a thread-safe version of the MySQL client library with the `–enable-thread-safe-client’ configure option. This creates a `libmysqlclient_r’ library with which you should link your threaded applications. See *Note threaded-clients::.

So what I was missing was the option
–enable-thread-safe-client

Below is the working config options that I’ve used:
./configure –prefix=/opt/mysql_5.0.45 –with-extra-charsets=complex –with-unix-socket-path=/opt/mysql-5.0.45/tmp/mysql.sock ;
make ; make install

The mysql5 libraries have been installed in:
/opt/mysql-5.0.45/lib/mysql

Now mysql5 libraries has to be added to the shared library path, add the following line to: /etc/ld-elf.so.conf
/opt/mysql-5.0.45/lib/mysql
Reload the ldconfig
/etc/rc.d/ldconfig restart

Remember to create /opt/mysql-5.0.45/my.cnf and change the port number so it doesn’t conflict with the mysql4 instance.
Now mysql5 is ready to be started!