Always rely on unixODBC each time a port is looking for libodbc.so
Remove odbc compat from libiodbc
This allows to install both kde and gnome at the same time
While here:
- Convert libiodbc to USES=libtool
- Convert a bunch of libiodbc dependencies to USES=libtool
- Chase libiodbc.so shlib change
- Stagify some ports
- Convert some ports to USES=pgsql
Discussed with: rakuco (kde)
With hat: portmgr
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
Right now this is a noop in the former case and a noop in the latter
case unless lang/gcc44 has been installed explicitly.
This puts a bit more emphasis on standardizing on a canonical version
"current" GCC and makes it easier to update that canonical version
by changing the default in Mk/bsd.gcc.mk and updating the lang/gcc port.
That is, USE_GCC=yes means "use a decent/modern version of GCC" without
having to worry about details.
Approved by: portmgr (bdrewery)
This port is indented for developers and port maintainers. It is a
copy of lang/erlang with a few differences:
- Nothing is installed in $PREFIX/bin
- Libraries are installed in $PREFIX/lib/erlang15
- You have to change your PATH to actually use it
- Support for building PLTs is removed
- Other ports are not supposed to install anything inside this environment
What is this for:
- Building Erlang applications using the R15 runtime, once R16 is
committed (think Riak).
- Building Erlang applications when there are conflicts with modules
provided by other ports (for example, the RabbitMQ client libraries
conflict with the server code installed by net/rabbitmq).
- Testing new Erlang versions before the main port is upgraded.
