/usr/portage/profiles/base/profile.bashrc should have ${PN}:${SLOT} in the following line: for conf in ${PN} ${PN}-${PV} ${PN}-${PV}-${PR}; do
Created attachment 103754 [details, diff] Patch to profile.bashrc
Wondering what for exactly, it's not like anyone would be allowed to use ${PN}:${SLOT} syntax anywhere in the official tree, current stable portage doesn't understand it.
I'm of the opinion that the chunk of code that's currently in base/profile.bashrc shouldn't really be there since it's easy enough for users to add it to /etc/portage/bashrc if they want per-package env like that. So, I'll leave this for others to deal with. :)
(In reply to comment #0) > /usr/portage/profiles/base/profile.bashrc should have ${PN}:${SLOT} in the > following line: > for conf in ${PN} ${PN}-${PV} ${PN}-${PV}-${PR}; do > This has nothing to do with the portage team imho; go ask on the Gentoo-Dev ML.
(In reply to comment #4) > This has nothing to do with the portage team imho; Not me, but Jakub Moc assigned this bug to Portage team.
(In reply to comment #2) > Wondering what for exactly, it's not like anyone would be allowed to use > ${PN}:${SLOT} syntax anywhere in the official tree, current stable portage > doesn't understand it. > This isn't related in any way to similar (the same) syntax which could be used in ebuilds or command line. It's in BASH for loop, so it's harmless to stable Portage.
We don't maintain profile.bashrc.
Move this to gentoo-dev mailing list. Thanks.
Just use [[ "${SLOT:-0}" == "0" ]]; syntax in a given env file. I'd rather us not change that code. It only exists as a stopgap till portage itself can support pkg env using proper atoms.