[yocto] Bitbake recipe Post install script not executed once the package is installed

[Paul Eggleton]

On Saturday 14 March 2015 11:37:51 Bipnesh, Abhinav wrote:
> Paul Eggleton wrote:
> > On Saturday 14 March 2015 10:39:59 Bipnesh, Abhinav wrote:
> > > I was trying to perform a post install activity as part of the recipe
> > > using pkg_postinst_PACKAGENAME() but seems it’s not working. Below is
> > > the sample function we have written as part of the recipe
> > > 
> > > pkg_postinst_test (){
> > > 
> > >     #!/bin/sh -xe
> > >     echo " we are calling post install for test"
> > >     mkdir -p /test/logs/1
> > >     touch /test/test1/test2/test3/sample.txt
> > > 
> > > }
> > > testX directory exists as they are created as part of the install
> > > activity.
> > > When we verify the post install we did find the file being created as
> > > below is the output
> > > 
> > > ls /test/test1/test2/test3/.txt ls: cannot access
> > > /test/test1/test2/test3/.txt: No such file or directory
> > 
> > I assume you meant *.txt as .txt wouldn't exist even if the postinstall
> > script had run.
> > 
> > > Also didn't see the echo output on the console when the package is being
> > > installed or post installation activity is being performed.
> > 
> > Is the output package that you are installing actually called "test"?
>
> Yes, Basically I did install manually using below command
> rpm -i test.rpm

I meant at the build system end. Is there a "test" directory under packages-
split under the workdir for the recipe? You can find the workdir by running:

 bitbake -e recipename | grep ^WORKDIR=

Just checking, is DISTRO or MACHINE set to "test"? Does "test" appear anywhere 
in the value of OVERRIDES? You can check by running:

 bitbake -e | grep ^OVERRIDES=

> One thing to add here is we are running Busybox on which I am trying to
> perform the installation.

That shouldn't matter.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre