Then this would be a rfe/idea or a defect. I think the gap in communication here is support could be saying something like "The behavior you describe is how the product is currently designed to function - since you think it should behave in a different way can you make a case for this being a rfe/idea or defect" and then they can take the next appropriate step.
i have had the whole "by (wrong) design" discussion before and 'wrong' is always subjective. the design was possibly 'correct' at the time it was written due to some constraint - and that may change over time, or it may really be 'wrong' in light of reality but that requires some kind of change request and investigation to the impact of making the change, and if it would break some other use case (probably not in this specific case). we have had customers ask for a feature to be 1 or 0 because each views their version as 'correct', and those are always fun to navigate.
Point taken and it can be subjective.
Although in this case I struggle to think of why anyone would want a new RedHat or Windows system package without the ability to easily select the packages from a check list
Well – I agree w/ you on this specific one ☺
I fwd’d this along to the support managers as well.