The ebuild for util-linux-2.13.1 stopped honoring the crypt USE flag in preference for the otherwise much clearer and more descriptive loop-aes USE flag. Unfortunately, this change has been implemented with only a silent 'elog' entry and no transitional period. Given the criticality of this flag for (some) people's systems, a gentler approach to introduce this change would have been to WARN people and allow for a transitional period with BOTH flags accepted. I'll attach my proposed patch for the ebuild. (Hmm... shouldn't this be possible right away, when filing a bug?)
Created attachment 148852 [details, diff] Patch for a more gentle ebuild to allow breaking fewer systems for those of us with attention deficit For the benefit of the paranoid, who have most of their system encrypted, but fail to read every single line printed by emerge...
i'm not putting things back under USE=crypt read your messages, they're there for a reason
Whatever... it's your call. I still think that - changing critical flags without proper warning and a transitional period allowing both variants to work is a bad idea; - at a minimum, 'elog' should be changed to 'ewarn'; so, that the message gets picked up and repeated _in_a_visually_obvious_manner_ (i.e. NOT all green) at the end of a long build.
i'll make the ewarn change, but that's it
