Mailinglist Archive: opensuse-packaging (74 mails)

[Michal Marek <mmarek@xxxxxxx>]

Hi,

does anyone an idea how to solve situations like this in a "right way"?
There is an application A and a library L and libL-plugin for app A. The
user installs A and L and wants to use L features from A. Another user
installs just A and is not interrested in L. Now if A would require or
recommend libL-plugin, then installing A would automatically pull the
(possibly big and unwanted) library L. Requiring or recommending
libL-plugin in L would have the same problem.

To give a real example:
A = unixODBC
L = mysql-shared (or postgresql-libs)
libL-plugin = MyODBC-unixODBC (or psqlODBC)

Both unixODBC and mysql-shared can be used without each other, but the
user somehow expects, that if he or she installs unixODBC and
mysql-shared, it will simply work with each other. See this bug:
https://bugzilla.novell.com/show_bug.cgi?id=144602

Other example is php5 and it's extensions (databases again for example),
some multimedia players and codec libraries probably have a similar problem.

Any ideas?

--
Michal Marek
SuSE CR

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging-unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging-help@xxxxxxxxxxxx