Re: testForLib not always detecting libraries in local install
"Isak Savo" <[email protected]>
| Newsgroups | gmane.comp.autopackage.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Jun 1, 2008 at 11:02 AM, Leslie Newell <[email protected]> wrote: > > 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. Does it work if you log-out/log-in again (or even reboot the computer)? -Isak --------------------------------------------------------------------- To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected] For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]