1 |
On Tue, Dec 01, 2015 at 09:00:55AM -0800, Zac Medico wrote: |
2 |
> On 12/01/2015 08:50 AM, William Hubbs wrote: |
3 |
> > The "container" keyword, being generic, would have its meaning expanded |
4 |
> > to cover new container systems as they come along. This means if a |
5 |
> > service script has the keyword "-container" it will not work under any |
6 |
> > current or future container systems. On the other hand, adding |
7 |
> > "container" means it will work under all of them. |
8 |
> |
9 |
> If it's similar to how license groups work, then there is room for doing |
10 |
> things like "-@container docker" which means no containers except |
11 |
> docker, or "@container -docker" which means all containers except |
12 |
> docker. Keyword groups can be implemented using a simple expansion |
13 |
> mechanism, just like license groups. |
14 |
|
15 |
Keyword groups are an interesting idea; I'll think about this approach. |
16 |
|
17 |
William |