With a recent update, all of a sudden, cryptsetup and related packages were being pulled in. It seems this is due to the update to sys-fs/udisks-2.7.4, which contains the dependency >=sys-libs/libblockdev-2.14[cryptsetup,lvm?] Should this be >=sys-libs/libblockdev-2.14[cryptsetup?,lvm?] so with a conditional for cryptsetup as well?
Starting with version 2.7.0, udisks really has a hard dependency (build and runtime) on the libblockdev crypto plugin, meaning libblockdev[cryptsetup]. I suppose we should remove the USE flag from udisks since the dependency on cryptsetup is now effectively unconditional.
See https://github.com/storaged-project/udisks/pull/195/files for the upstream PR that introduced the hard dependency.
(In reply to Alexandre Rostovtsev from comment #1) > Starting with version 2.7.0, udisks really has a hard dependency (build and > runtime) on the libblockdev crypto plugin, meaning libblockdev[cryptsetup]. Ok, thanks for the info. > I suppose we should remove the USE flag from udisks since the dependency on > cryptsetup is now effectively unconditional. I agree. This report can be closed then.
fixed in 2.8.0