| Re: [proaudio] jack-audio-connection-kit |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] jack-audio-connection-kit
- From: Karl Lindén <spray.sucks@xxxxxxxxx>
- Date: Sun, 24 Mar 2013 18:14:56 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=400iSWHIs8rb+x+3fpnFuDwkHtTzoRM8NEIJBLJY0rI=; b=eYWj/XYS38pluzAhAZvcN2oAGSwp0km2DWGewKIaXUpPb7+2EZ7FulHx8zyc4W5bBw wsXV51Eyjv9qCs8wXtiS4uD2kMHYxDm1J2zxPxe5+cLRRXjAekvT/5yl/jq74/sBqZYE zujh0AqrSdkGjtDucMKMQek0MFR60+7XTVUZKtnDH3YhVWHsFG3yxAZrUCKQuppwCDYq n6SemGcX3rpmVPL8WKbcu/eRiCStyvdZEBUPttCm2pC2oDWr/TBLsnAcW0A9HSG0yq92 n/ihd5Etr/bg8myCocQWyxDrufGcXMVaqF6gbtqkp34DnscRj4taj2vH23ceHB1FkEwX aFHw==
Nice. I'm still a little leery to the slotting due to collision risk,
but the virtual thing might have some advantages. If you for example
would want to have JACK1 installed you would now have to mask versions
newer than 0.121.3 (because all versioned jack ebuilds are keyworded
with ~arch) or else the JACK will be updated on emerge -u. Using
media-sound/jack1 and media-sound/jack2 would remove that problem. As
there are collisions between the two they have to block each other
until there are no conflicting files.
I think it is best if the conflicts are removed upstream so that we do
not have to do nasty unofficial patches.
The problem with the virtuals is that it might delay the stabilization
(both jack1 and jack2 have to have stable ebuilds for virtual/jack to
be allowed to be stable). However, that is not a problem until
media-libs/libffado is marked as stable (it is forcing jack to be
marked unstable).
I think the DBus can be handled by symlinking
/usr/share/dbus-1/services/org.jackaudio.service to either one of
jack1 and jack2 but I'm not completely sure.
Regards,
Karl
2013/3/24 Manuel Bärenz <manuel@xxxxxxxxxxx>:
> Hi,
>
> Well I was just starting to work on an eselect to make make all the
> symlinks work. However, I didn't give the DBus issue a thought, so maybe
> I'll report back once I've finished working on my local overlay.
>
> I wanted to have the different slots in order to test the US122L driver
> more thoroughly with JACK and cleanly separate driver problems and
> JACK1/JACK2 issues. I could just install one of the JACKs locally, but I
> thought it might be nicer to have the slot solution. However, if it's
> too messy, I'm not going to force it.
>
> About the virtual package: What advantage would that have? I admit that
> it captures the idea of JACK 1 and 2 being essentially different
> software doing roughly the same job more nicely than having different
> versions, but I can't think of any practical uses. And how would you go
> around the file conflicts? It would make it no easier, I guess.
>
> Best, Manuel
>
>