On Thu, Jul 10, 2003, Matthias Kurz wrote:
> [...]
> And while i'm at it: looks like a zero byte file "openpkg.boot.install.sh"
> survives the cleanup in the end of the build ;-)
> [...]
Hmmm... that's the only code in the bootstrap procedure which
creates such a openpkg.boot.install.sh file:
| # install package via RPM spec file by faking a
| # sufficiently enough RPM run-time environment
| runscript () {
| step=$1
| script="$tmpdir/openpkg.boot.$step.sh"
| echo ". $prolog" >$script
| sed -e "/^%$step/,/^%/ p" -e 'd' <$spec | \
| sed -e '/^%/d' | \
| sed -e 's;%{SOURCE \([^ ]*\.tar[^ ]*\)};${RPM_DIST_DIR}/\1;g' \
| -e 's;%{SOURCE \([^ ]*\)};${RPM_SOURCE_DIR}/\1;g' | \
| sed -e 's;%{[?]\([^:}]*\):\([^}]*\)};${\1+\2};g' \
| -e 's;%{![?]\([^:}]*\):\([^}]*\)};${\1-\2};g' \
| -e 's;%{[?]\([^:}]*\)};${\1+""};g' \
| -e 's;%{![?]\([^:}]*\)};${\1-""};g' \
| -e 's;%{\([^}]*\)};${\1};g' >>$script
| echo "++ executing(%$step): sh $script"
| sh $script
| if [ $? -ne 0 ]; then
| rm -f $script
| echo "$0:ERROR: script returned non-null value"
| exit 1
| fi
| rm -f $script
| }
| runscript prep
| runscript build
| runscript install
And I cannot see why $script should be left over. It is removed both for
the error and ok situation. Hmmm... sorry, I've no clue why this file
was zero length and how it could survive...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
