Newer Portage versions throw a post install notice about the metadata-transfer feature flag being removed by default, asking the user to take care about it. On the one hand a certain number of users will miss the message and on the other hand it's unclear to me why Joe User should be bothered: When FEATURES in /etc/make.conf doesn't hold metadata-transfer or -metadata-transfer, Portage could imply it, in case PORTDIR_OVERLAY doesn't hold any overlays with eclasses. Another option would be to bind the implicitness of metadata-transfer to PORTAGE_ECLASS_WARNING_ENABLE="1", instead checking the overlays. This would lower the impact of the default configuration change on the user side as well as it meant less invalid bug reports, would therefore be a win for devs and users.
(In reply to comment #0) > Newer Portage versions throw a post install notice about the metadata-transfer > feature flag being removed by default, asking the user to take care about it. Ebuilds no longer contain this warning, so apparently it's irrelevant now.
