--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The problem I see is in regards to how a group could actually be used to maintain a state.
Groups aren't/can't be versioned. They are merely repo-side lists.
Furthermore, there is no yum functionality that adddesses a group once it is installed (except deletion which can have untoward consequences if an ungrouped dependant should unknowingly be removed) Once installed, the packages are addressed as any other individually installed package.
Again, with a yum group, there is nothing granular enough to be able to determine whether or not a specific state has been reached or breached and in need of repair.
It would seem to me that this is a problem that can already be addressed with a state definition that enumerates the required packages. If you're lookimg for a less verbose solution, a wrapper rpm cam be easily created that does nothing more than carry the list of desired packages as dependencies. (see https://github.com/jordansissel/fpm for an easy-mode utility for rolling a variety of different package types)
I'd just hate to see the yum package handling state module become bloated trying to account for all of the weird bits that trying to inject package groups would bring about.
-S
--