Hey, I noticed that the check_mk_agent package from my overlay is masked because someone masked it globally. I get the masking for the outdated package in ::gentoo, but not globally? So at the moment I have to unmask my overlay package. Reproducible: Always Steps to Reproduce: emerge world or check_mk_agent Actual Results: package is globally masked Expected Results: package should only be masked for ::gentoo
Overlays inherit package.mask from their master repos. I believe this is the intended behavior.
Hmm, i guess, normally overlays have a metadata/layout.conf with masters = gentoo to use the global eclasses, etc. So, that means to also receive the global package masks? My questions is, why are these global masks not like this net-analyzer/check_mk_agent::gentoo ? It has the same consequence for all the global masked packages but doesn't affect packages in overlays.
I don't think PMS allows for the repository to be specified as part of the mask entry. That's a Portage-specific extension, and cannot be used in gentoo.git.
We could certainly prevent package.mask entries from propagating from master repos to overlays. We could could make it conditional on layout.conf and/or repos.conf settings.
(In reply to Mike Gilbert from comment #3) > I don't think PMS allows for the repository to be specified as part of the > mask entry. That's a Portage-specific extension, and cannot be used in > gentoo.git. Yeah it's not allowed, but we can change the way portage propagates the package.mask entries. It can modify behavior based on layout.conf and/or repos.conf settings.
