[PATCH] gen_build_files.sh: Remove bashisms

[Cristian Ionescu-Idbohrn]

On Sun, 16 May 2010, Rob Landley wrote:

> On Saturday 15 May 2010 17:27:40 Cristian Ionescu-Idbohrn wrote:
> >
> > Thank you.
> >
> > I had a look through and found:
> >
> > ,----[ individual ]
> >
> > | possible bashism in individual line 15 (brace expansion):
>
> He changed the start to #!/bin/bash and you're still looking for bashisms.

Yes, I do.

> If you keep on with this, I'm going to go through and try to optimize
> every shells cript in the project with as many intentional obscure
> bashisms as possible.

Oh boy...  But then you'll also have to imitate those "many intentional
obscure bashisms" in hush, will you not?

> (Keep in mind dash doesn't even support thing/{one,two} syntax.

I know.  But that would easily be made portable with a for loop, wouldn't
it?

> it's not hard to make the scripts smaller and simpler by filling them
> with things dash can't cope with.)

True.

> I'm warning you to drop this topic.

Threat.  It was not my intention to get you irritated to that degree, but
now that I managed, I think I'll go on for a while longer :)

> I don't have a stubborn streak, I have a vindictive streak.  It has a
> very high activation threshold, and most things I don't care enough to
> do anyhing about.  But once the straw breaks the camel's back

English is not my mother tongue, but what you say sounds good :)

> you go in the Bruce Fucking Perens category

You don't seem to like that man.  I don't know him, never met, but I bet
Bruce won't be happy to find out about his new middle name, so I won't
Cc:.

I guess I'll have to be more careful here.  I might get an additional
middle name(s) and be unhappy for the rest of life :)

> and I remain 100% opposed to your very existence years later.

Sad thing :(

But, we could still have fun discussing how we go about making the scripts
as portable as possible and avoid breaking peoples builds, I presume.
And this is, IMO, the main point to this flamy exchange of ideas.

Take care Rob.  And try to focus on the matter at hand, which should not
be "which shell is best", but how to make the scripts portable.


Cheers,

-- 
Cristian