(2013-01-23, 13:49)da-anda Wrote: Problem: User get's confronted with "addon XY updated" notifications for addons that he never installed but where dependencies of some other addon. This confuses users, they should only see the notification if they installed the addon. Same for addons marked as broken etc.

Solution: Keep track if addons are installed by the user or as part of a dependency and only show notifications if they where installed by the user.

So adding a column to the DB + object that keeps track if installed by the user or not could be used to solve both issues.

(2013-01-23, 14:03)Montellese Wrote:

(2013-01-23, 13:49)da-anda Wrote: Problem: User get's confronted with "addon XY updated" notifications for addons that he never installed but where dependencies of some other addon. This confuses users, they should only see the notification if they installed the addon. Same for addons marked as broken etc.
Solution: Keep track if addons are installed by the user or as part of a dependency and only show notifications if they where installed by the user.

I had a PR for this half a year or so ago, see PR1398 but the opinions seem to be very different so I closed it again. If you feel like it you can write your opinion in the PR. Maybe it could be solved with a setting because I'm sick of all the "foo has been installed" and "foo has been updated" for addons I never manually installed. The PR only addresses the first notification, but with some extra logic I'm sure the second one (notification on update) could be addressed as well.