Comment 11 for bug 434173

I'm not entirely sure what the best course of action is here for update-manager in the release-upgrade context.

When update-manager runs on jaunty it will not have check-language-support available. So it either needs to embed a copy of it or run it after the upgrade has finished. This would add additional step (something I dislike) or make it part of the cleanup process (where it does not belong).

Additionally in the context of upgrades we do not want to add stuff during the upgrade that the user may have refused explicitely (e.g. because the download size for some of the help files is too big or because he does not need it). That means that u-m needs to run a "check-language-support" before the upgrade to see what is missing now and after the upgrade to see whats missing then and just install the new dependencies. If the list of the new/changed dependencies is small, we could ship that instead of a a full copy of the check-language-support code.