On 12/01/2015 08:50 AM, William Hubbs wrote: > The "container" keyword, being generic, would have its meaning expanded > to cover new container systems as they come along. This means if a > service script has the keyword "-container" it will not work under any > current or future container systems. On the other hand, adding > "container" means it will work under all of them.
If it's similar to how license groups work, then there is room for doing things like "-@container docker" which means no containers except docker, or "@container -docker" which means all containers except docker. Keyword groups can be implemented using a simple expansion mechanism, just like license groups. > The more I think about this, I think fine-grained control rather than > just using a single keyword for all containers is the better option. Keyword groups, as described above, result in a flexible combination of both approaches. -- Thanks, Zac
