The hardened-profile package.use declares "dev-lang/python gdbm". USE="gdbm" is already part of the base-profile make.defaults, so it is no longer necessary for the hardened profile to declare it. The problem arises when other profiles, such as musl, declare USE="-gdbm" and are overridden by the hardened-profile. This override does not seem intentional! It seems to stem from a python interaction that causes gdbm to be used over berkdb (the previous, less secure, default), therefore hardening it. However, as stated prior, this is no longer necessary and may cause regressions in a parent profile. --- P.S. The musl-profile USE="-gdbm" itself might be outdated. It *may* have stemmed from a time where gdbm could not be compiled without glibc.
