The following reply was made to PR docs/172692; it has been noted by GNATS.

From: Michael Telahun Makonnen <[email protected]>
To: Chris Rees <[email protected]>
Cc: [email protected], [email protected], 
 "[email protected]" <[email protected]>
Subject: Re: docs/172692: [PATCH] Bring parts of the rc scripting guides up
 to date
Date: Thu, 18 Oct 2012 09:57:49 +0300

 On 10/15/2012 09:26 PM, Chris Rees wrote:
 
 >> Not sure why you felt this paragraph needed to be removed.
 >
 > Because the style is clearer and makes it much more obvious when a
 > variable is having its own default value set.  In ports at least, the
 > current style is to use the less verbose form.
 >
 
 ok
 
 >
 >> While you are technically correct, I think you misunderstood the
 >> writer's intent, which was to show how an rc.conf(8) variable can be
 >> used in a subroutine to control the behavior of the command.  I agree
 >> that the example isn't a very good one (in that it doesn't depict a
 >> valid use case), but I think the "spirit" is correct.  Maybe you can
 >> suggest a better example?
 >>
 >
 > I think that this script is very simple by design, and making a better
 > example would complicate it.  It is definitely worth pointing out the
 > alternative though; it makes useful food for thought; both examples
 > with a disclaimer.
 
 ok
 
 >
 > [1] http://www.bayofrum.net/~crees/patches/rc-scripting-modernise2.diff
 >
 
 Looks fine to me. Thanks for taking the time to update the documentation.
 
 Cheers,
 Mike.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-rc
To unsubscribe, send any mail to "[email protected]"

Reply via email to