On 29/10/2008, at 3:42 AM, Erik Ljungstrom wrote:
> Unless there are any objections to that solution, I'll do a proper
> diff
> against the .sh script rather than its product and put it in my
> branch?
My main concern with this particular patch (great fast involvement
btw, thanks!) is that it introduces a dependency on sed.
While I think sed will generally be present on any baseline install,
there are some varieties... are these sed lines generic enough to not
break anywhere? And what happens if sed does not exist or chucks an
error?
Can this somehow be resolved without non-shell foo?
I was thinking about simply double-listing each option that has a dash
in it, but there may be better ways.
Cheers,
Arjen.
--
Arjen Lentz, Director @ Open Query (http://openquery.com.au)
Training and Expertise for MySQL in Australia and New Zealand
Hi Erik
On 29/10/2008, at 3:42 AM, Erik Ljungstrom wrote:
> Unless there are any objections to that solution, I'll do a proper
> diff
> against the .sh script rather than its product and put it in my
> branch?
My main concern with this particular patch (great fast involvement
btw, thanks!) is that it introduces a dependency on sed.
While I think sed will generally be present on any baseline install,
there are some varieties... are these sed lines generic enough to not
break anywhere? And what happens if sed does not exist or chucks an
error?
Can this somehow be resolved without non-shell foo?
I was thinking about simply double-listing each option that has a dash
in it, but there may be better ways.
Cheers, openquery. com.au)
Arjen.
--
Arjen Lentz, Director @ Open Query (http://
Training and Expertise for MySQL in Australia and New Zealand
OurDelta: free enhanced builds for MySQL @ http:// ourdelta. org