![]() ![]() |
Apr 13 2008, 02:57 PM
Post
#1
|
|
|
Group: Members Posts: 69 Joined: 23-March 05 Member No.: 6,696 |
"This package seems to depend on other packages. Please install them too"
lol How on earth am i supposed to figure out what its talking about as the packages I downloaded didn't come with a txt file to point out dependencies. Gus |
|
|
|
Apr 13 2008, 03:26 PM
Post
#2
|
|
|
Group: Members Posts: 69 Joined: 23-March 05 Member No.: 6,696 |
"This package seems to depend on other packages. Please install them too" lol How on earth am i supposed to figure out what its talking about as the packages I downloaded didn't come with a txt file to point out dependencies. Gus Could this be the answer I am looking for? http://www.users.on.net/~hluc/myZaurus/custom.html#kismet |
|
|
|
Apr 14 2008, 08:05 AM
Post
#3
|
|
![]() Group: Members Posts: 1,837 Joined: 31-December 05 From: Illinois USA Member No.: 8,821 |
Meanie's site is full of useful information.
If you install a package in Cacko/Sharp and get the above message, just uninstall it, then open a console and install it this way. Then you'll get more useful messages as to what the dependencies are. CODE ipkg install /home/Documents/Install_Files/packagename.ipk Your path to your new package may be different, just change the path accordingly. Another method to find dependencies, is to search the forum, or find a feed that has the same package and download the "Packages" file. The "Packages" file is just a text file and should have a description and dependencies listed for your package. If you use Windows to try to read the "Packages" file, just open it in wordpad, and copy/paste it to notepad and save as Packages.txt Wordpad will convert the utf8 text formatting to something you can read in windows. |
|
|
|
Apr 14 2008, 08:07 AM
Post
#4
|
|
|
Group: Members Posts: 69 Joined: 23-March 05 Member No.: 6,696 |
Meanie's site is full of useful information. If you install a package in Cacko/Sharp and get the above message, just uninstall it, then open a console and install it this way. Then you'll get more useful messages as to what the dependencies are. CODE ipkg install /home/Documents/Install_Files/packagename.ipk Your path to your new package may be different, just change the path accordingly. Anopther method to find dependencies, is to search the forum, or find a feed that has the same package and download the "Packages" file. The "Packages" file should have a description and dependencies listed for your package. You are a life saver and a genius |
|
|
|
Apr 14 2008, 09:23 PM
Post
#5
|
|
|
Group: Members Posts: 454 Joined: 17-November 05 Member No.: 8,551 |
What ever happened to the simplicity of just running the standard "ldd" command?
http://sdjf.esmartdesign.com/commands/ldd.html It doesn't come on the Z, but is easy to get and use. sdjf |
|
|
|
Apr 15 2008, 03:52 AM
Post
#6
|
|
|
Group: Members Posts: 124 Joined: 16-January 05 Member No.: 6,248 |
What ever happened to the simplicity of just running the standard "ldd" command? it's not useful if you can't find the name and version of the package that contains a suitable copy of the missing shared library, or if the dependency isn't a shared library at all but something else fortunately, the package dependencies are stored in the package file: CODE tar zxOf whatever.ipk ./control.tar.gz | tar zxOf - ./control | grep '^Depends: '
|
|
|
|
Apr 17 2008, 12:29 AM
Post
#7
|
|
|
Group: Members Posts: 454 Joined: 17-November 05 Member No.: 8,551 |
Okay, thanks, I guess it only simplifies some of the time.
sdjf |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 25th May 2013 - 01:34 AM |