I’m trying to make a qpr package of a BSP and I experiencing some problems.
Here’s the scenario:
I make the package with following command (the default values are taken from
the previous package):
packager -p -m hicosh4-1.0beta-emtrio.qpr hicosh4/
when the packager asks for a install script I give it the post-install.sh
which is located in the working directory.
After answering the questions the qpr package is ready without errors.
If I now install the package I can find following messages from the packager
log messages.
----------- snip --------------
08:05:59 STATUS: Script: Executes a post-install blocking script
(rep://emtrio/hicosh4/core-1.0beta/scripts/post-install.sh). (HiCOSH4
1.0beta Beta release 12)
08:06:00 STATUS: Script complete (Executes a post-install blocking script
(/bin/ksh -c
“/pkgs/repository/emtrio/hicosh4/core-1.0beta/scripts/post-install.sh”).)
------------ snap -------------
There are no messages indicating any errors. However, If I now look at the
pkgs directory I see that the
/pkgs/repository/emtrio/hicosh4/core-1.0beta/scripts/post-install.sh
file is not there!?
I can find the /pkgs/repository/emtrio/hicosh4/core-1.0beta directory, but
it contains no “scripts” dirrectory.
Oddly the installer didn’t complain about executing a script which doesn’t
exist.
After building the package my package source directory (hicosh4) contains
the script with following path:
/root/hicosh4/emtrio/hicosh4/core-1.0beta/scripts/post-install.sh
I don’t know why it is there and the next time I try to make the package the
packager complains :
“Searching for all files to include…
Warning: Uncommon directory paths have been detected.
[problem: emtrio]
[caused by: hicosh4//emtrio]”
This problem is solved by removing the emerged path, but it’s surely not
meant to be that way, right?
Am I missing something here? Are there any known “gotchas” when working with
the packager install scripts?
Thanks for any help
I got it working by including my post-install.sh script to the package
sources and telling that the installer should run a “command” instead of a
“private script”. I’m not that happy with the solution cause the package now
includes something which doesn’t belong there.
I also noticed that even though I tell the packager that the return value of
the script/command should be checked, the installer never gives any error
messages no matter what the return value is. It also “runs” scripts that do
not exist without giving any errors. This means that if my install script
fails the customer doesn’t get informed about it. I’m considering of writing
a README to tell the customers run the script manually. At least they’ll
know if something went wrong.
Has anyone else experienced this kind of behaviour with the
packager/qnxinstall system or is it just me?
“Martin Nylund” <mnylund@emtrion.de> schrieb im Newsbeitrag
news:c5h1r4$q2f$1@inn.qnx.com…
I’m trying to make a qpr package of a BSP and I experiencing some
problems.
Here’s the scenario:
I make the package with following command (the default values are taken
from
the previous package):
packager -p -m hicosh4-1.0beta-emtrio.qpr hicosh4/
when the packager asks for a install script I give it the post-install.sh
which is located in the working directory.
After answering the questions the qpr package is ready without errors.
If I now install the package I can find following messages from the
packager
log messages.
----------- snip --------------
08:05:59 STATUS: Script: Executes a post-install blocking script
(rep://emtrio/hicosh4/core-1.0beta/scripts/post-install.sh). (HiCOSH4
1.0beta Beta release 12)
08:06:00 STATUS: Script complete (Executes a post-install blocking script
(/bin/ksh -c
“/pkgs/repository/emtrio/hicosh4/core-1.0beta/scripts/post-install.sh”).)
------------ snap -------------
There are no messages indicating any errors. However, If I now look at the
pkgs directory I see that the
/pkgs/repository/emtrio/hicosh4/core-1.0beta/scripts/post-install.sh
file is not there!?
I can find the /pkgs/repository/emtrio/hicosh4/core-1.0beta directory, but
it contains no “scripts” dirrectory.
Oddly the installer didn’t complain about executing a script which doesn’t
exist.
After building the package my package source directory (hicosh4) contains
the script with following path:
/root/hicosh4/emtrio/hicosh4/core-1.0beta/scripts/post-install.sh
I don’t know why it is there and the next time I try to make the package
the
packager complains :
“Searching for all files to include…
Warning: Uncommon directory paths have been detected.
[problem: emtrio]
[caused by: hicosh4//emtrio]”
This problem is solved by removing the emerged path, but it’s surely not
meant to be that way, right?
Am I missing something here? Are there any known “gotchas” when working
with
the packager install scripts?
Thanks for any help