El dom, 11-01-2015 a las 08:11 -0500, Rich Freeman escribió: [...] The main issue I see is that the main objective of using games.eclass is to keep games being used by people in "games" group... but this point if broken as soon as we allow packages to not use that eclass and, then, I see no advantage at all on not deprecating games.eclass (even not killing it immediatly... but at least to let people know that it's deprecated finally) (I am thinking in repoman warning about that eclass usage as it does for old python eclasses and many more)
But I guess this should be moved back to current games team and maybe QA as I agree escalating it to the Council directly looks "excessive"
