-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18-07-2012 21:09, Michał Górny wrote:
> On Wed, 18 Jul 2012 23:03:14 +0200 Peter Stuge
> wrote:
>
>> William Hubbs wrote:
>>> let's move all of the discussion of this to the bug if possible
>>> so that it is all in one place.
>>
>> That's fine an
On Wed, 18 Jul 2012 23:03:14 +0200
Peter Stuge wrote:
> William Hubbs wrote:
> > let's move all of the discussion of this to the bug if possible so
> > that it is all in one place.
>
> That's fine and probably good.
>
> Note that you were the one inviting email discussion about the
> change. I
William Hubbs wrote:
> let's move all of the discussion of this to the bug if possible so
> that it is all in one place.
That's fine and probably good.
Note that you were the one inviting email discussion about the
change. I guess you wanted rather to focus on the question if
breaking compatibili
Folks,
let's move all of the discussion of this to the bug if possible so that
it is all in one place.
Thanks,
William
pgpw1garAIRzQ.pgp
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 04:09 PM, William Hubbs wrote:
>
> The other approach, which is on the bug, still has this issue,
> e.g.
>
> /etc/init.d/foo command1 arg1 arg2 command2 arg3 arg4 command3
> arg5
>
> gets pretty ugly pretty quick. which arguments go wi
On Wed, Jul 18, 2012 at 03:58:18PM -0400, Michael Mol wrote:
> On Wed, Jul 18, 2012 at 3:49 PM, Peter Stuge wrote:
> > William Hubbs wrote:
> >> /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
On Wed, 18 Jul 2012 14:41:52 -0500
William Hubbs 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:
>
> /e
On 18-07-2012 15:58:18 -0400, Michael Mol wrote:
> > along with all other commands can work like before.
> >
> > /etc/init.d/foo stop -- start
> >
> > can pass start as an argument to the stop command.
>
> I like this approach, because its use of -- continues expected
> commandline parsing behavio
On Wed, 18 Jul 2012 15:58:18 -0400
Michael Mol wrote:
> On Wed, Jul 18, 2012 at 3:49 PM, Peter Stuge wrote:
> > William Hubbs wrote:
> >> /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
On Wed, Jul 18, 2012 at 3:49 PM, Peter Stuge wrote:
> William Hubbs wrote:
>> /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?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/07/12 03:49 PM, Peter Stuge wrote:
> William Hubbs wrote:
>> /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.
>>
>> W
William Hubbs wrote:
> /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?
/etc/init.d/foo stop start
along with all other commands c
All,
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
13 matches
Mail list logo
