public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] New virtual: virtual/jack for jack protocol implementations
@ 2016-02-04 14:05 Alexis Ballier
  2016-02-06 10:51 ` Luca Barbato
  2016-02-08  7:48 ` [gentoo-dev] " Mart Raudsepp
  0 siblings, 2 replies; 4+ messages in thread
From: Alexis Ballier @ 2016-02-04 14:05 UTC (permalink / raw
  To: gentoo-dev; +Cc: suhr, proaudio

Hi,

We've been supporting jack sound server [1] for a long time.
Currently, we're supporting jack1 as
media-sound/jack-audio-connection-kit. However, jack2 has been out for
quite some time.

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/1aebd8e72ff4ff2665761fc3b07f796945aa0943

Best regards,

Alexis.


[1] http://www.jackaudio.org/
[2]
https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] New virtual: virtual/jack for jack protocol implementations
  2016-02-04 14:05 [gentoo-dev] New virtual: virtual/jack for jack protocol implementations Alexis Ballier
@ 2016-02-06 10:51 ` Luca Barbato
  2016-02-08  7:48 ` [gentoo-dev] " Mart Raudsepp
  1 sibling, 0 replies; 4+ messages in thread
From: Luca Barbato @ 2016-02-06 10:51 UTC (permalink / raw
  To: gentoo-dev

On 04/02/16 15:05, Alexis Ballier wrote:
> Hi,
> 
> We've been supporting jack sound server [1] for a long time.
> Currently, we're supporting jack1 as
> media-sound/jack-audio-connection-kit. However, jack2 has been out for
> quite some time.
> 
> 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/1aebd8e72ff4ff2665761fc3b07f796945aa0943
> 
> Best regards,
> 
> Alexis.
> 
> 
> [1] http://www.jackaudio.org/
> [2]
> https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2
> 

Sounds a good idea.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [gentoo-dev] Re: New virtual: virtual/jack for jack protocol implementations
  2016-02-04 14:05 [gentoo-dev] New virtual: virtual/jack for jack protocol implementations Alexis Ballier
  2016-02-06 10:51 ` Luca Barbato
@ 2016-02-08  7:48 ` Mart Raudsepp
  2016-02-08 10:57   ` Alexis Ballier
  1 sibling, 1 reply; 4+ messages in thread
From: Mart Raudsepp @ 2016-02-08  7:48 UTC (permalink / raw
  To: gentoo-dev; +Cc: suhr, proaudio, gstreamer

Ü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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Re: New virtual: virtual/jack for jack protocol implementations
  2016-02-08  7:48 ` [gentoo-dev] " Mart Raudsepp
@ 2016-02-08 10:57   ` Alexis Ballier
  0 siblings, 0 replies; 4+ messages in thread
From: Alexis Ballier @ 2016-02-08 10:57 UTC (permalink / raw
  To: gentoo-dev

On Mon, 08 Feb 2016 09:48:22 +0200
Mart Raudsepp <leio@gentoo.org> wrote:

[...]

> 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.

Yes, the point is that is has same library name and ABI.
Diffing installed headers show a very few symbols that are jack2 only,
but packages needing them should depend on jack2 not the virtual, if
there are any.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-02-08 10:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-04 14:05 [gentoo-dev] New virtual: virtual/jack for jack protocol implementations Alexis Ballier
2016-02-06 10:51 ` Luca Barbato
2016-02-08  7:48 ` [gentoo-dev] " Mart Raudsepp
2016-02-08 10:57   ` Alexis Ballier

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox