Agreed. As jason said, if we cannot come up with easy to understand rules
for overrides, we should not have them at all.
Which is what I said in the initial proposal:
Allow <include/>, but without the ability to re-declare subsystems within the
inclusion hierarchy.
On Jul 5, 2011, at 6:11 PM, Brian Stansberry wrote:
An abstract profile only offers a benefit if we allowed a profile
that
inherits another profile to override subsystems.
It's not a huge benefit though; probably not worth it. The junior admin
at 3AM could still easily go into profile A intending to only affect the
servers in group A and unknowingly update the group B servers as well.
The odds of his doing that might be slightly reduced, since there would
be no servers running profile A directly so he might be more inclined to
understand the implications of his change.