All recent ebuilds for sys-fs/udisks have an unconditional dependency on >=sys-fs/lvm2-2.02.66. The ./configure for udisks does have an option --disable-lvm2. In a system that does not use lvm, there is no reason to have this package. Reproducible: Always Steps to Reproduce: 1. emerge udisks or something that requires it. 2. emerge brings in lvm2, even if you have no other need for it 3. Actual Results: lvm2 is required by udisks Expected Results: udisks should be able to emerge without lvm2 There is more discussion at forum topic 878413, and this seems a bit parallel to bug 354635, and although that is for kdelibs requiring udisks, the logic is similar.
lvm2 includes device-mapper, and there is no flag to disable device-mapper in udisks, therefore lvm2 is really required even with --disable-lvm2
It does seem a bit strange, but why can't you have device-mapper without lvm?
(In reply to comment #2) > It does seem a bit strange, but why can't you have device-mapper without lvm? Because device-mapper/lvm2 upstream merged device-mapper as part of lvm2 package. And we are not in business of countering upstreams decisions, as in, we don't split packages unless it's for solving circular dependencies or such. You could try to contact lvm2 upstream and try to make them split device-mapper into it's own package... but honestly, I don't think it's worth it.
