Bug #9126 Automated setup of ODBC driver
Submitted: 11 Mar 2005 14:50 Modified: 19 Jul 2007 1:39
Reporter: Jan Wedekind Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S4 (Feature request)
Version:3.51 OS:Linux (GNU/Linux)
Assigned to: Kent Boortz CPU Architecture:Any

[11 Mar 2005 14:50] Jan Wedekind 
Description:
The ODBC driver still has to be configured either by the user or by a client application. Exspecially the library-names of the driver and the setup-dialog are not easy to find out and differ with the distribution. This makes it impossible to develop a user-friendly application using unixODBC, which would run on arbitrary distributions of Linux.

[myodbcdriver]
Description             = MySQL ODBC 2.50 Driver DSN
Driver          = /usr/lib/unixODBC/libmyodbc3.so
Setup           = /usr/lib/unixODBC/libodbcmyS.so.1

How to repeat:
No need to repeat.

Suggested fix:
For example installing an rpm-packages of sqsliteodbc (see http://www.ch-werner.de/sqliteodbc/) will not only install the library but also setup the entry for the ODBC-driver using the odbcinst-tool. Afterwards ODBCConfig would be ready for setting up datasources.
[19 Jul 2007 1:39] Kent Boortz 
The RPMs now register and unregister the driver
when needed. There are now two RPMs, the driver
RPM and the "setup" RPM, and the driver information
is updated depending on if one or both are installed.

We will look into creating some sort of generic
Unix/Linux install/uninstall script, similar to
the ones for Windows, but for now we target to 
make sure that packages that contains an installer
application also register the driver.