On Fri, Oct 05, 2007, Christoph Schug wrote:
> On Fri, Oct 05, 2007, Ralf S. Engelschall wrote:
>
> > On Fri, Oct 05, 2007, Joerg Lehrke wrote:
> >
> > > The problem is caused by following block within the shtool install
> > > function:
> > > [...]
> >
> > Ah, I see. Well, mysql.spec's usage of "s
On Fri, Oct 05, 2007, Ralf S. Engelschall wrote:
> On Fri, Oct 05, 2007, Joerg Lehrke wrote:
>
> > The problem is caused by following block within the shtool install
> > function:
> > [...]
>
> Ah, I see. Well, mysql.spec's usage of "shtool subst" with _arbitrary_
> complex sed(1) style "-e" opt
On Fri, Oct 05, 2007, Joerg Lehrke wrote:
> The problem is caused by following block within the shtool install
> function:
> [...]
Ah, I see. Well, mysql.spec's usage of "shtool subst" with _arbitrary_
complex sed(1) style "-e" options is already the source of the trouble.
I'll see what we can do
The problem is caused by following block within the shtool install
function:
# adjust the target file
if [ ".$opt_e" != . ]; then
sed='sed'
OIFS="$IFS"; IFS="$ASC_NL"; set -- $opt_e; IFS="$OIFS"
for e
do
sed="$sed -e
On Thu, Oct 04, 2007, Joerg Lehrke wrote:
> I know that IRIX is not a supported platform, but the problem I found there
> can be avoided easily. /bin/sh messes up the opt_e string within the install
> command of shtool. Especially the MySQL RPM build fails on IRIX because of
> this. Since OpenPKG
I know that IRIX is not a supported platform, but the problem I found there
can be avoided easily. /bin/sh messes up the opt_e string within the install
command of shtool. Especially the MySQL RPM build fails on IRIX because of
this. Since OpenPKG provides a BASH this shell should be used for a
