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