Ühel kenal päeval, N, 04.02.2016 kell 15:05, kirjutas Alexis Ballier: > As its name does not imply, jack2 is not really the successor of > jack1 > but rather another implementation of the same protocol [2]. As such, > I > don't think it is wise to add jack2 as an update to jack1 in > media-sound/jack-audio-connection-kit but rather to add a new package > (media-sound/jack2) along with a virtual that packages can depend > onto. > > Proposed ebuild for the virtual is here: > https://github.com/suhr/gentoo/commit/1aebd8e72ff4ff2665761fc3b07f796 > 945aa0943 >
Does it work with media-plugins/gst-plugins-jack too (as in, can jackaudiosrc read from jack2 and jackaudiosink output to it)? :) If yes, feel free to adjust deps there accordingly once you implement the virtual, or maybe chat with miknix too. However one concern with the virtual - if it is not interchangeable (same library naming and ABI), then you have to rebuild things against the other provider, and hopefully that can be set up to be more automatic somehow; as the virtual will be satisfied with either of them, so the user could exchange them without actual consumers linking to it noticing. Some thoughts into that aspect, if even just some warning to user, would be good. Mart
