Easy Clearing Out Unused Dependencies

[Sheila]

I've installed, reviewed and then uninstalled a bunch of packages. How do I get rid of installed dependencies I don't need anymore? ie How do I check for 'orphans'?

[jcabrer]

I've installed, reviewed and then uninstalled a bunch of packages. How do I get rid of installed dependencies I don't need anymore? ie How do I check for 'orphans'?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102159\"][{POST_SNAPBACK}][/a][/div]

Unfortunately, ipkg does not support removal of deps.  I guess this feature was sacrificed to keep it small.  Big brother apt-get does handle deps.

If you don;t mind the extra work involved, you can read the Packages file in the feeds and it will list deps.  Then you can manually remove the ones that you think you don't need.  Be aware that sometimes when building ipk files, some of us don't bother listing deps, and sometimes list things as deps that really are not deps for that package.

[lardman]

Unfortunately, ipkg does not support removal of deps.

That's a sweeping statement and it's not quite true. I suppose the version which is used with pdaXrom doensn't support this, however the re-written OZ version does (yes, I know this is the pdaXrom bit of the forum).

I would however be interested in an app which produces a dependency tree for all of the ipks on the system (prefereably with a package size too) so that I could go through and remove things which I don't think I need.


Si

[Sheila]

I would however be interested in an app which produces a dependency tree for all of the ipks on the system (prefereably with a package size too) so that I could go through and remove things which I don't think I need.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102220\"][{POST_SNAPBACK}][/a][/div]

Gentoo's command is: emerge --depclean --ask

[koen]

Unfortunately, ipkg does not support removal of deps.

That's a sweeping statement and it's not quite true. I suppose the version which is used with pdaXrom doensn't support this, however the re-written OZ version does (yes, I know this is the pdaXrom bit of the forum).
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

OZ (and OE) only use the releases of ipkg, closely guarded by PierLuigi, the ipkg maintainer. So either pdaX uses an archaic version or the below statement is true:

I guess 'ipkg -h' or reading [a href=\"http://handhelds.org/moin/moin.cgi/Ipkg]http://handhelds.org/moin/moin.cgi/Ipkg[/url] is too hard for some people:

Code: [Select]

usage: ipkg [options...] sub-command [arguments...]
 where sub-command is one of:

 Package Manipulation:
 update                         Update list of available packages
 upgrade                        Upgrade all installed packages to
                                latest version
 install                  Download and install
                                (and dependencies)
 install             Install package
 configure []              Configure unpacked packages
 remove                   Remove package
 flag ...         Flag package(s)
                                (=hold|noprune|user|ok|installed|unpacked (one per invocation))

 Informational Commands:
 list                           List available packages and descriptions
 files                    List all files belonging to
 search                  Search for a package providing
 info [pkg []]           Display all/some info fields for or all
 status [pkg []]        Display all/some status fields for or all
 download                 Download to current directory.
 compare_versions (compare versions using <= < > >= = << >>)
 print_architecture             prints the architecture.
 print_installation_architecture
 whatdepends [-A] [pkgname|pat]+
 whatdependsrec [-A] [pkgname|pat]+
 whatprovides [-A] [pkgname|pat]+
 whatconflicts [-A] [pkgname|pat]+
 whatreplaces [-A] [pkgname|pat]+

 Options:
 -A                             Query all packages with whatdepends,
                                whatprovides, whatreplaces, whatconflicts
 -V                     Set verbosity level to . If no value is
 --verbosity            provided increase verbosity by one. Verbosity levels:
                                        0 errors only
                                        1 normal messages (default)
                                        2 informative messages
                                        3 debug output
 -f                 Use as the ipkg configuration file
 -conf              Default configuration file location
                                is /etc/ipkg.conf
 -d                 Use as the the root directory for
 -dest              package installation, removal, upgrading.
                                 should be a defined dest name
                                from the configuration file, (but can also
                                be a directory name in a pinch).
 -o              Use as the root directory for
 -offline        offline installation of packages.
 -verbose_wget                  more wget messages

 Force Options (use when ipkg is too smart for its own good):
 -force-depends                 Make dependency checks warnings instead of
                                errors and install/remove package in spite of
                                failed dependences
 -force-defaults                Use default options for questions asked by
                                ipkg. (no prompts). Note that this will not
                                prevent package installation scripts from
                                prompting.
 -force-reinstall               Allow ipkg to reinstall a package.
 -force-overwrite               Allow ipkg to overwrite files from another
                                package during an install.
 -force-removal-of-dependent-packages
 -force_space                   Install even if there does not seem to be
                                enough space.
 -noaction                      No action -- test only
 -nodeps                        Do not follow dependences
 -recursive                     Allow ipkg to remove package and all that
                                depend on it.
 -test                          No action -- test only
 -t                             Specify tmp-dir.
 --tmp-dir                      Specify tmp-dir.
-force-removal-of-dependent-packages or  -recursive  would be what you are searching for

[Sheila]

I guess 'ipkg -h' or reading http://handhelds.org/moin/moin.cgi/Ipkg is too hard for some people:
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102356\"][{POST_SNAPBACK}][/a][/div]

- I guess assuming that people haven't run 'ipkg -h', gives you a right to accuse others of laziness. FYI, if you run 'ipkg -h' on a 3100 running pdaXrom '-force-removal-of-dependent-packages or -recursive', is not shown as the help file is apparently truncated. The info. I needed is in your post. Thank you. That's what these forums are for. So, I'm lazy? You did not check to see what the actual output of 'ipkg -h' was on the machines we're running. THAT is lazy. You ASSUMED I am illiterate. But, it didn't stop you from making a personal attack. Now, why don't you make a guess as to a word I'm thinking of to describe your snide remark? The first three letters are identical to, and have the same number of letters as a capitalized word above...
- I'll try your suggestion and read the link. Thanks again.

[lardman]

So, I'm lazy? You did not check to see what the actual output of 'ipkg -h' was on the machines we're running. THAT is lazy. You ASSUMED I am illiterate.

Koen said this:

OZ (and OE) only use the releases of ipkg, closely guarded by PierLuigi, the ipkg maintainer. So either pdaX uses an archaic version or the below statement is true:

I guess 'ipkg -h' or reading http://handhelds.org/moin/moin.cgi/Ipkg is too hard for some people:

It's an either, or. Either pdaXrom doesn't use the official release, or people don't read ipkg -h.

Regards,


Simon

[pgas]

Let's stop this here.
 
In brief:

- pdaxrom version of ipkg doesn't provide a way to remove dependencies, ipkg is a shell script in pdaxrom
- there is a newer version (implemented in C)  available in OZ, that  does this.

I am not sure that the newest version is usable as it is (even if recompiled) in pdaxrom as if I am not mistaken it  uses ar  rather than tar.gz

[lardman]

Let's stop this here.

Quite.

I am not sure that the newest version is usable as it is (even if recompiled) in pdaxrom as if I am not mistaken it uses ar rather than tar.gz

The latest version would be useable if taken an OE sharprom-compat build or built using the pdaXrom system; otherwise I certainly replaced the pdaXrom version with an OZ binary version when I was trying pdaXrom out (this was about a year ago this April), this may have come from OZ 3.2, I don't remember.

It can use ar, however it's also perfectly happy installing tar.gz formatted ipks. The only issue you might find is that the later versions of ipkg are far stricter about the contents of control files than the earlier versions ever were, so this may cause issues - I don't know.


Si

[clofland]

With the frequent release of new RC's, I think most of us just reflash and reinstall and that cleans up all of our dependencies.

Some of us have a Windows background, and so we are used to formatting our machine regulary to clean them up.

Seriously, though, maybe when pdaXrom comes to another stable release, this will be a bigger issue to more people.

As it is, I find that the package manager in pdaXrom already works much better than the one in SharpROM (and clones). I can even use the GUI with confidence. The GUI package install in SharpROM was evil in my opinion. Maybe it was just the lack of any visible output though.