On Thu, Dec 16, 2010 at 2:47 PM, Andrew Flegg <[email protected]> wrote:
> 1) A meta-package, as Ville describes, which depends on the two packages. > This might live in 'user/' (TBD) and be called something like > "qt-community-fixes-1". I don't think this should be a general > "community hotfixes", because then it makes no sense for QML apps > to depend on it in general. However, the SSU could depend on it to > pull it in more widely. > > 2) A change to Packages which just checks for the appropriate hotfix > packages; i.e. instead of depending on one metapackage, instead > QML projects have to depend on both fix packages. > > Given the problems with HAM & meta-packages in the past, I'd like to > know we were confident in the behaviour if we took option #1. > > IMO #2 is a no-go actually (which makes #1 the only way :), as if we allow per-hotfix dependencies, we will have a mix of hotfixes that HAM will never allow to nicely upgrade (if you have fix A as part of the hotfix metapackage, and then with the next iteration a B hotfix comes, HAM will actually refuse to install an app requiring hotfix B because that would require updating A, but that was part of another app -> you get a 'problems' tab). Some PyQt users might find this scenario familiar, so I suggest we actually encourage to serve the fixes in bundles - that would also make testing easier, etc).
_______________________________________________ maemo-community mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-community
