Thomas Tanner wrote:
Forced upgrades of some components for installation of a new package is standard practice for all package management systems (keyword version dependencies). I think the main problem is that the mp-fremantle-pr packages hardcodes the exact version of all PR packages instead of specifying the minimum version. If a user could selectively upgrade a core package without conflicting with mp-fremantle-pr they would not be forced to completely upgrade the firmware for new extras apps. (BTW, the broken dependency specification in the PR also makes it impossible to remove unnecessary language packs)
I agree with you completely with your first post, however, you touched on why Maemo doesn't work this way.
For the time being, the proposal Niels suggested is the least messy. We're not creating a new Maemo 5 sub-version this way.
Maemo/Nokia folks - is there any plans on implementing the brainstorm idea[1] on open-source packages any time before MeeGo? This would alleviate some of the update mess. Closed binaries could then be included into a smaller "Maemo 5" update that can work with the Extras repo without having to branch it.
[1] http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
_______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
