On Tue, Dec 01, 2015 at 09:11:45AM -0600, William Hubbs wrote: > On Tue, Dec 01, 2015 at 12:24:05AM +0000, Robin H. Johnson wrote: > > Rather than replacing all of the system-specific keywords, can we make > > 'container' into an alias that expands to the full list of known container > > types? That way, if there is an init script that is specific to some > > container > > type, it would still be usable. > > This is the approach I would personally be more comfortable with.
Thinking about this more, there definitely is a concern imo. 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. 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. Thoughts? William
signature.asc
Description: Digital signature
