Seems like eclass appends it to KF6 versions as well.
pardon?
It is strange to see the kf6compat for KF6 packages themselves, and it is not required by the KF5 conterparts, so I assumed it is a mistake: $ emerge -pv kde-frameworks/kguiaddons:5 These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 5.45 s (backtrack: 0/20). [ebuild U *] kde-frameworks/extra-cmake-modules-9999::kde [5.113.0::gentoo] USE="-doc -test" 0 KiB [ebuild NS *] kde-frameworks/kguiaddons-9999:6/9999::kde [5.113.0:5/5.113::gentoo] USE="X dbus wayland -debug -doc -test (-kf6compat%)" 0 KiB [ebuild R ] kde-frameworks/kguiaddons-5.113.0:5/5.113::gentoo USE="X dbus kf6compat* wayland -debug -doc -test" 0 KiB [blocks b ] kde-frameworks/kguiaddons:5[-kf6compat(-)] ("kde-frameworks/kguiaddons:5[-kf6compat(-)]" is soft blocking kde-frameworks/kguiaddons-9999)
Please show an example where SLOT=6 has USE=kf6compat added.
Are you misinterpreting "(-kf6compat%)" there?
Ah, that '%', of course! I thought portage does not apply that for new slots, and was mistaken. Sorry for bothering you!