With the removal of sys-fs/e2fsprogs-libs, and the addition of the "tools" USE flag to build the ext2fs headers, some packages will fail to build without the tools USE flag enabled (see bug 833110, for example). I don't understand the rationale for ever building e2fsprogs without tools, but I assume that some reason exists for it.
(In reply to ta2002 from comment #0) > With the removal of sys-fs/e2fsprogs-libs, and the addition of the "tools" > USE flag to build the ext2fs headers, some packages will fail to build > without the tools USE flag enabled (see bug 833110, for example). I don't > understand the rationale for ever building e2fsprogs without tools, but I > assume that some reason exists for it. https://bugs.gentoo.org/806875#c2 is why.
(In reply to Sam James from comment #1) > (In reply to ta2002 from comment #0) > https://bugs.gentoo.org/806875#c2 is why. That certainly makes sense, although I would have handled it with a "minimal" USE flag that (implicitly) warns the user that expected functionality might not exist in a package built with that flag.