testForLib not always detecting libraries in local install

Leslie Newell <[email protected]>
Newsgroups gmane.comp.autopackage.devel
Message-ID <[email protected]>
Hi,

I have a package that installs some shared libraries. It is possible 
that the user may already have those libs on their system so I use 
testForLib in the skeleton to test for the individual libraries.

I do the following on a distro that does not currently have Autopackge 
(Ubuntu 8):
Install my libs.package from a terminal. This downloads the Autopackage 
core. When it asks for a password I say 'no password' so it installs in 
the home directory.
I now double click on myapp.package which depends on these libs. The 
package uses the skeleton to find the libs but testForLib fails to find 
them.
I now run package install myapp.package from a terminal and testForLibs 
works. This is repeatable. If I double click it fails, if I use a 
terminal it works.

Here is the [Test] section from my skeleton. I know it is inefficient 
but I am not very experienced with shell scripts.

[Test]

liblist="bindadv bindaui bindbase bindcore bindgl bindhtml bindnet 
bindrichtext bindstc bindxml bindxrc lua luadebug luasocket"
for lib in $liblist; do
    res=0
    testForLib libwxlua_gtk2u_wx${lib}-2.8.so && res=1
echo $res
    if [ $res = 1 ]
    then
        echo "libwxlua_gtk2u_wx${lib}-2.8.so found"
    else
        echo "libwxlua_gtk2u_wx${lib}-2.8.so not found"
        return
    fi
done
INTERFACE_VERSIONS=28.0

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.