Bug 353371 – x11-libs/qt-sql with mysql: update RUNPATH for next generation installs

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Ingo Krabbe 2011-02-01 07:42:52 UTC]

Programs linked against qt-sql don't want to care about complexities finding mysqlclient, when they use the mysql plugin.
Newer(beta) builds of mysql/mariadb currently don't link the mysqlclient library to /usr/lib* and personally I hope they continue doing so, when they get stable.
So qt-sql needs to install the mysql plugin with a library run-path (-R)

Reproducible: Always

Steps to Reproduce:
1.Install a mysql/mariadb from mysql overlay with some ~* beta flag
2.update qt-sql with use mysql
3.see your applications don't find the MYSQL* databases. (for example mythtv)



Expected Results:  
Dependent applications shouldn't need to care about internals of the mysql client plugin.

[Comment 1 Ingo Krabbe 2011-02-01 07:44:33 UTC]

Created attachment 261216 [details, diff]
patch for the current qt-sql ebuild

[Comment 2 Davide Pesavento (RETIRED) 2011-02-01 22:00:42 UTC]

(In reply to comment #0)
> Programs linked against qt-sql don't want to care about complexities finding
> mysqlclient, when they use the mysql plugin.
> Newer(beta) builds of mysql/mariadb currently don't link the mysqlclient
> library to /usr/lib* and personally I hope they continue doing so, when they
> get stable.
> So qt-sql needs to install the mysql plugin with a library run-path (-R)
> 

Yes, I totally agree with this.

However, is it really necessary to add the additional RPATH to everything that is built by qt-sql ebuild? Wouldn't libqsqlmysql.so be sufficient?

[Comment 3 Davide Pesavento (RETIRED) 2012-04-01 16:19:43 UTC]

(In reply to comment #2)
> However, is it really necessary to add the additional RPATH to everything
> that is built by qt-sql ebuild? Wouldn't libqsqlmysql.so be sufficient?

I don't want to add random rpaths to libraries that don't need them. So please reopen when you have provided an answer to the above question.