As it is now, packages can have their own individual make.conf(5) environment variable additions by being listed in /etc/portage/package.env and an equivalent file with the environment being created under /etc/portage/env/, with the package.env file referring to it. e.g. ~ # grep lvm2 /etc/portage/package.env sys-fs/lvm2 unwanted-sysfs-lvm2 ~ # cat /etc/portage/env/unwanted-sysfs-lvm2 INSTALL_MASK="${INSTALL_MASK} /etc/dmtab" I am looking to make this a bit more flexible and automatic. Users should just be able to create a file with the environment variables, and Portage should pick it up. For example, I could have created that environment file as '/etc/portage/env/sys-fs/lvm2/unwanted' or just '/etc/portage/env/sys-fs/lvm2', and there could be an optional token in FEATURES to enable this new behaviour (in case this enhancement would cause a problem for existing users with strange env/ directory layouts). Is this proposal acceptable?
