View Single Post
wicket's Avatar
Posts: 634 | Thanked: 3,266 times | Joined on May 2010 @ Colombia
#354
Originally Posted by shmerl View Post
@wicket: You are free to discuss this problem with Mer developers on the mailing list or the IRC channel. I think there are good solutions for that - to make some metapackages with bundles - default with some packages restricted to GPLv2, and optional ones where those packages will be replaced with updated versions even if they are GPLv3. So if vendors care - they'll use GPLv2 bundles. And if not - they'll use unrestricted ones. And users will be able to simply replace default ones with optional if they need to.
Unfortunately when you introduce such meta-packages you introduce fragmentation in OS compatibility. If a vendor chooses to Tivoize their Sailfish product it's likely that they won't let you replace packages in the core OS. You'll have devices that allow meta-packges where your app will run but it won't run in those Tivoized devices.

Last edited by wicket; 2013-02-25 at 04:10.
 

The Following User Says Thank You to wicket For This Useful Post: