Yes, and I actually see this as a feature, since there is no "apt-get upgrade" functionality in the Application Manager. Users would get the newer vesion of cairo by accident, when they install or upgrade a non-hidden package that depends on cairo.
Semi-related: how about an "Upgrade All" button on the "Check for Updates" page?
Not exactly: we do not only want to control which individual packages you can install, but also which combinations. Say there is a new version of cairo, but we figure out that we also need to upgrade the internet radio applet since it had a bug that--by chance--wasn't triggered by the old version of cairo. So we want to only support the new cairo together with the new radio applet. With a version locked meta package, we can make sure that the user gets the right combinations of packages.
Wouldn't you just use standard dependencies for this? Make the new radio applet depend on the new cairo? -- It doesn't take a nukular scientist to pronounce foilage! --Marge Simpson http://www.gnu.org/philosophy/shouldbefree.html _______________________________________________ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
