eix-sync/update-eix doesn't takes into account PORTDIR_OVERLAY defined in /etc/portage/profile/make.defaults. Reproducible: Always Steps to Reproduce: 1. Define PORTDIR_OVERLAY in /etc/portage/profile/make.defaults 2. Comment that PORTDIR_OVERLAY in /etc/make.conf Actual Results: update-eix doesn't parse PORTDIR_OVERLAY Expected Results: update-eix does parse PORTDIR_OVERLAY
Really don't see why would anyone define any overlay there; the file there is to *override* current profile defaults, not to stick contents that clearly belongs to /etc/make.conf there.
I agree here with Jakub. eix should be compatible with standard usage of portage, not with every exotic portage feature (which change too often). Putting typical /etc/make.conf variables into /etc/portage/profile/make.defaults is certainly not a standard usage.
If you are managing several machines with _almost_ same configuration it's really useful. It's not so hard to add PORTDIR_OVERLAY in every make.conf, so you are obviously right, as soon as eix supports reading USE from /etc/profile/portage/make.defaults
To avoid a misunderstanding: eix *does* parse /etc/profile/portage/make.defaults and you can use it to override most variables (like e.g. ACCEPT_KEYWORDS). Hence, the summary is wrong (but I don't have the rights to change it). Just some variables, including PORTDIR and PORTDIR_OVERLAY, are treated specially by eix for several reasons. For example, if a make.default of some overlay changes PORTDIR_OVERLAY, chaos would be perfect: What should be the content of the database? Moreover, eix has options to ignore local settings, and if these options would change the available overlays (but of course not the eix database), these options would lead to strange behavior. Thus, I consider this bug as WONTFIX (but I do not have rights to change its state).
Well. Fixing summary and status.
