On Wed, 18 Jul 2012 14:41:52 -0500 William Hubbs <willi...@gentoo.org> wrote:
> I have received a request to allow OpenRC's init scripts to take > command line arguments [1]. As noted on the bug, there are some > advantages to this, but implementing it would have to break backward > compatibility, for example: > > /etc/init.d/foo stop start > > would no longer work the way you might expect because there would be > no way to tell whether start is a command or an argument to stop. > > What are your thoughts about this change? As I see that the discussion is now in two places, I'd shortly repeat what I said on the bug. First of all, I believe that you are focusing too much on your proposed solution and too little on the actual problem. For example, in this mail the actual problem is just linked as a footnote. This means that we are starting to discuss the solution not knowing what it will be for. As I mentioned there, I see that the problem covers a wide case of script 'multiplexing', 'templates' or 'virtual script generators', however you want to call it. I don't really think command-line arguments can handle that. They will just add complexity to the issue. For example, how would you consider the state of such a script? Will every status check require passing additional arguments? Will every script using this technique be required to re-invent the whole multiplexing concept? -- Best regards, Michał Górny
signature.asc
Description: PGP signature
