On Wednesday, 3 April 2019 02:37:46 BST Rich Freeman wrote: > Just set USE="-cryptsetup -dmraid ..." and turn off whatever other > flags you object to.
I did that, and also masked sys-fs/cryptsetup to enforce it. Emerge did indeed complain loudly, and its dependency chain report clearly implied that libblockdev was the cause, which is why I suspected that IUSE statement (thanks for the explanation of its meaning). "emerge --info | grep -e dmraid -e device-mapper -e lvm -e cryptsetup" returned null. I may take the path of least resistance and just let it insist on the bloat. > Of course you should understand the implications, but these particular flags > probably aren't really used for anything unless you are actually using LVM/ > LUKS/etc. I'd be careful about just turning off random flags unless you > understand what they do. There are those who set -* in their make.conf and > then go whitelisting whatever they need. IMO that is a lot of pain for not > a lot of gain, except maybe in odd niches or for those with OCD... :) I agree - and resisting lvm and crypt feels similar. I hope I'm not developing that condition... -- Regards, Peter.
