As per #259508, a new bug. I do not have an ebuild, but I have seen that jack2 uses waf for build scripts. It seems like this new version has a lot of improvements over jack1, which has always been a bit of a mess. Reproducible: Always Steps to Reproduce:
I spent hours to try to make an ebuild, giving up now. The ebuild is probably one of the dirtiest ever made, but as is the build system (waf). It was impossible for me to make it install in the image directory without having the dynamic linking of the library pointing to /var/tmp/... ! Waf experts welcome. Currently the ebuild doesn't work (wap install fire some lib in /, hopefully jack2 is not a common lib name). Some hours ago I was able to make a clean installation, but, as said before, jackd2 was looking for /var/tmp/portage/media-sound/jack-audio-connection-kit-1.9.2/image/usr/lib/jack2....
Created attachment 186818 [details] ebuild attempt, currently not working This ebuild is not really dangerous as I will not even overwrite jack's one (bunch of sed to change simulate a slot). (Exception of jack.pc in pkgconfig) but it still has to be modified in order to work properly. The problem is mainly due to waf as builder so, no emake, no sandbox :[
pro-audio has an ebuild for 1.9.2. it worked fine here, although it doesn't really slot cleanly (the binary is still called jackd, etc)
*** Bug 161127 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > pro-audio has an ebuild for 1.9.2. it worked fine here, although it doesn't > really slot cleanly (the binary is still called jackd, etc) > 1.9.5 is currently in the proaudio overlay and the ebuild is far proper. I think this bug, and maybe #295215 can be closed.
*** Bug 295215 has been marked as a duplicate of this bug. ***
jack-audio-connection-kit-1.9.8 is in pro-audio overlay: http://proaudio.tuxfamily.org/
whats keeping jack2 from being added to the tree? This bug report is from two years ago, and the proaudio overlay has been maintaining ebilds for jack2 for some time already.
Fixed. Please close. commit bc49b1935922e0cba177804e039900c830a23f6f Author: <D0><A1><D1><83><D1><85><D0><B0><D1><80><D0><B8><D0><BA> <suhr@i2pmail.org > Date: Tue Feb 2 03:56:25 2016 +0300 media-sound/jack2: new JACK2 ebuild
If you want to introduce the new name "jack2", you need to introduce a virtual ebuild for JACK and make all the relevant ebuilds depend on it instead of media-sound/jack-audio-connection-kit. Or you can do it the easy way and make it media-sound/jack-audio-connection-kit-1.9.10 like they do in the 'proaudio' overlay. Maybe masked so you don't force the upgrade. Right now, media-sound/jack2 is unusable because any package requiring JACK will replace it with JACK1.
This is fixed. Please close. commit bc49b1935922e0cba177804e039900c830a23f6f Author: <D0><A1><D1><83><D1><85><D0><B0><D1><80><D0><B8><D0><BA> <suhr@i2pmail.org> Date: Tue Feb 2 03:56:25 2016 +0300 media-sound/jack2: new JACK2 ebuild
The new ebuild has file collisions with media-sound/jack-audio-connection-kit, though. Is it considered to be working?
media-sound/jack-audio-connection-kit-1.9.11_rc1 is available in my overlay: https://github.com/stefantalpalaru/gentoo-overlay
there has been media-sound/jack2 for a while
(In reply to Alexis Ballier from comment #14) > there has been media-sound/jack2 for a while There are 81 packages in the main tree depending on "media-sound/jack-audio-connection-kit" instead of "virtual/jack", rendering "media-sound/jack2" unusable.
