"caps" and "jack-caps" are both responsible for a sys-libs/libcap dependency Reproducible: Always Steps to Reproduce: 1. # grep caps /usr/portage/profiles/use.local.desc app-crypt/gnupg:caps - Use Linux capabilities library to control privileges. media-sound/jack-audio-connection-kit:jack-caps - enable capabilities 2. # grep libcap /usr/portage/media-sound/jack-audio-connection-kit/jack-audio-connection-kit-0.94.0.ebuild /usr/portage/app-crypt/gnupg/gnupg-1.2.3-r5.ebuild /usr/portage/media-sound/jack-audio-connection-kit/jack-audio-connection-kit-0.94.0.ebuild: jack-caps? ( sys-libs/libcap ) /usr/portage/app-crypt/gnupg/gnupg-1.2.3-r5.ebuild: caps? ( sys-libs/libcap ) Expected Results: Isn't that redundant? Maybe leave only "caps" and change the jack ebuild
Torbenh, I think this is a good idea. I think we might want to consider adding it as a global use flag since ebuilds other than gnupg and jack will probably want to use it too...
yeah that would be nice. but how do we tell people ? and we still dont have this use flag in the kernels. with 2.6 its only a matter of installing my LSM refined by jack`O`Quinn.. but with a 2.4 it requires a 2 line patch in the kernel. but i will change the USe flag when the next jack release comes out.
i'm going to change jack to use caps instead... iff jackcaps is set, it'll give them a message.
Done... caps is now a global use flag, and jack-caps has been removed... I left a check for it in the ebuilds which causes an eerror to be printed and the ebuild to exit.