Cacko Ipkg Dependancies, What's the magic 8-ball to learn deps? Options

[Sy Ali]

The package manager.. doesn't. It's just a frontend to the ipkg tools.

I searched around and found a reference to ldd, but that isn't right for ipk files.

The packaging guidelines say:

6.  The package control file should list all dependency information in the "Depends:" field.  All dependencies (libraries, etc.) should be on the feed as well.

How do I:
1. Determine the requirements of a particular package (before installing it)?
2. Determine the installed-size of a package before it is installed?
3. Determine the combined installed size of a package and all its dependancies?
4. Automatically install all dependancies?


1. Now I can see things like

CODE

ipkg depends <package>.ipk

which happens to have failed when I tried it thusly:

CODE

ipkg depends ruby_1.8.0-1_arm.ipk

ipkg_depends: ERROR: Package name ruby_1.8.0-1_arm.ipk contains illegal characters (should be [a-zA-Z0-0.+-])
error

ipkg info doesn't seem to do anything for that package.

Indeed it looks like running ipkg at the commandline is generally a bad idea, as I was unable to "manually" install ruby using the ipkg program. Strange.


2. I assume I can take a peek inside the archives and do some math. Is there a better way to do this?

3. Presumably this is possible with some scripting voodoo. Is there a better way?

4. Since viewing the dependancy of a package fails, I presume that this is impossible.

...

How does everyone else handle packages?

[Sy Ali]

CODE

# ipkg install ruby_1.8.0-1_arm.ipk

I did try this, but it didn't work as-expected. I was able to use the GUI tool -- after the silly wait for it to load everything up -- and then it would work.

Upon installing via the commandline, trying to run ruby gave me an error. I didn't have the forethought to record it though.