Apps Audit Still Can't FULLY Uninstall an Extension

[baz]

The work going into AppsAudit is great, but even with all the new features and functionality, the primary reason for a user to go there is missing: FULLY uninstalling an App. I want to be able to select a top-level app, and then have TC calculate and remove all its dependencies that are not required by any other program. To do that now you have to manually follow each dependency and it's dependencies and so on.

Thoughts?

[gerald_clark]

You can use "Not depended On" in the 2.9 rc series.
It will list all packages that are not used by other packages.
You can delete those you do not specifically want.

[roberts]

Unles a specific reproducible example is supplied say so doesn't really help.

[baz]

What do you mean? If you mark an app for deletion, it doesn't delete the dependencies too, does it?

[Kingdomcome]

Dependencies of one particular app might be needed by other apps still installed, therefore dependencies are not removed automatically.  As previously mentioned, 2.9 includes the added functionality of checking for extensions "Not depended on" which will help you weed out dependencies no longer needed.

[baz]

Right. Hopefully one day we can turn all that into a simple "Uninstall" button that does it all, and leave the AppsAudit for advanced uses.

[roberts]

It will delete the selected app and all of its dependencies not required by other exsiting extensions.

[baz]

I said "one day" not "today"!! Beautiful.   

[cjgau]

It seems that a semaphore is needed for each dependency; quite some bookkeeping...

if an app is "call"ed to be installed either as an independent app or as a dependency then its      semaphore++

Any app (or dependency) is "call"ed to be deleted    --semaphore   and check if (dependency==0) then delete

It's easy saying than achieving it.