The current list of profiles looks like [1] default/linux/amd64/10.0 [2] default/linux/amd64/10.0/desktop [3] default/linux/amd64/10.0/desktop/gnome [4] default/linux/amd64/10.0/desktop/kde * [5] default/linux/amd64/10.0/developer [6] default/linux/amd64/10.0/no-multilib [7] default/linux/amd64/10.0/server ... If I choose to go with "no-multilib", I loose all the benefits of the special gnome/kde/whatever profiles. But I have no reason to go with multilib, I have 64bit CPU and I compile everything from source so that I do not need any 32bit support. It just creates confusion because of the lib/lib64 issues etc. It would be nice to have the ability to choose between multilib/no-multilib for each profile flavour, at least until multilib is obsoleted and we get no-multilib by default. Reproducible: Always
Well I am not sure if kde/gnome can work with no-multilib support
They all work fine without multilib, but that's not a reason to add more profiles. Those "benefits" you get with the desktop profiles are just a different set of default USE flags. You can just switch to a no-multilib profile and change your make.conf. Take a look at ${PORTDIR}/profiles/targets/desktop/{gnome,kde}/{make.defaults,package.use} to see the difference. If there was a way to have the multilib feature as a switch, then that'd be indeed a nice solution, but that's not possible with the current profiles.
