Fix a very subtle gotcha in the pkgdef definition.
If the last (or only) section in a pkgdef file didn't end with a blank line then the 'section end' actions wouldn't be performed. The 'section end' marker is still a *single* blank line and if there are multiple sections in a pkgdef they *must* be seperated by such a line.
This commit is contained in:
parent
6d88b4bd9e
commit
152a6acd21
@ -334,6 +334,16 @@ parse_def()
|
|||||||
;;
|
;;
|
||||||
esac
|
esac
|
||||||
done < $metadir/pkgdef
|
done < $metadir/pkgdef
|
||||||
|
# If there is no blank line at the end of a pkgdef section (if there is only one section that is very
|
||||||
|
# likely) then we end up here without having executed the 'section end' actions (case '' above)
|
||||||
|
if [ $section -eq 0 ]; then
|
||||||
|
error $E_BAD_SECTION_END parse_def
|
||||||
|
else
|
||||||
|
section=0 # Finished this section
|
||||||
|
foundfiles=0 #
|
||||||
|
# Add scripts if requested
|
||||||
|
add_scripts $secname
|
||||||
|
fi
|
||||||
}
|
}
|
||||||
|
|
||||||
# check_unpackaged(): Check if there are unpackaged files in the stage area
|
# check_unpackaged(): Check if there are unpackaged files in the stage area
|
||||||
|
Loading…
x
Reference in New Issue
Block a user