Am Dienstag, 16. Dezember 2008 schrieb torbenh(a)gmx.de:
On Tue, Dec 16, 2008 at 12:31:22PM +0100,
oc2pus(a)arcor.de wrote:
Am Dienstag, 16. Dezember 2008 schrieb Thomas
Kuther:
@ oc2pus, jack in packman is broken, or YaST is.
I set up a fresh
install in a virtual machine using 11.1RC1 and only added packman.
Currently there is:
* pulseaudio-module-jack-0.9.12-8.5
* libjack0-0.116.1-0.pm.1
Now if I tick the box in YaST to install "jack" it pulls in
libjackserver2-0 and jack, which of course breaks things, as it keeps
libjack0. zypper on the other side gets it right. See the screenshot!
http://gimpel.ath.cx/~tom/jack_weirdness.png
nor the packman package or yast is broken...
pulseaudio-module-jack has a (wrong ?) requires to jack instead
libjack.so.1 (or a other program in your system) . And as there are more
than one provider for jack, yast pulls in the first provider for jack it
finds.
and this is only possible because, there are 2 packages, for libjack and
jack. Why do you think we distibute them in one package ?
They make no sense without each other.
STOP SPLITTING JACK UP.
This "fetaure" was not packman's idea ...
see openSuSE-shared-library policy:
http://en.opensuse.org/Shared_Library_Packaging_Policy
and even jack2 is providing this scheme:
http://trac.jackaudio.org/wiki/SuggestedPackagingApproach
* "jack server frontend" - virtual package provided by "jackd" and
"jackdbus"
packages
* "jack server (library)" - package containing libjackserver.so at least.
Maybe also: essential tools, drivers, inprocess clients.
* "jackd" - package containing jackd binary. This package depends on "jack
server (library)"
* "jackdbus" - package containing jackdbus binary and jack_control script.
This package depends on "jack server (library)"
* "jack client library" - package containing libjack.so
* "jack client library dev" - package containging headers and pkgconfig file
for libjack.so
* "jack server library dev" - package containging headers and pkgconfig file
for libjackserver.so
This shared library policy needs a lot of extra-work but it allows also to
update library packages without breaking existing packages and or
mass-rebuilds if a so-name of a library is changed (ffmpeg-libs, x264 are
well known candidates for changing often API).
And if we don't follow the naming-scheme of the base distribution we were lost
and have much more troubles.
have fun
Toni