FS#45578 - [zynaddsubfx] should depend on 'jack', not on 'jack2-dbus'
Attached to Project:
Community Packages
Opened by Hanspeter Portner (ventosus) - Tuesday, 07 July 2015, 13:27 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 08 July 2015, 09:17 GMT
Opened by Hanspeter Portner (ventosus) - Tuesday, 07 July 2015, 13:27 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 08 July 2015, 09:17 GMT
|
Details
Description:
All jack programs seem to depend on 'jack'. A user that uses 'jack' instead of 'jack2' or 'jack2-dbus' cannot install zynaddsubfx. Upgrade and/or installation of zynaddsubfx fails because of conflicting packages 'jack2-dbus' and 'jack'. zynaddsubfx thus should depend on 'jack', and not on 'jack2-dbus'... Additional info: * zynaddsubfx 2.5.1-1 Steps to reproduce: * sudo pacman -S jack * sudo pacman -S zynaddsubfx > jack2-dbus und jack stehen miteinander in Konflikt. jack entfernen? [j/N] |
This task depends upon
jack and jack2/jack2-dbus are API compatible.
Every other package in Arch which uses the JACK API, has 'jack' in its 'depends' field, NOT 'jack2' and NOT 'jack2-dbus'.
If you install jack2/jack2-dbus, they 'provide' 'jack', but not the other way round (e.g. 'jack' does not provide 'jack2/jack2-dbus'.
Users that prefer 'jack' still cannot install 'zynaddsubfx'.
Hint: portaudio already pulls in jack dependency, it may thus be omitted in the first place.
There is another issue: Thnigs get installed to /usr/lib64 (namcap)