View Single Post
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#352
Originally Posted by rcolistete View Post
Interesting part : "So we’ll start with one device, which we’ll announce soon, and afterward other devices will follow."
I read that article few days ago, I didn't find that part very interesting TBH, it's nothing more than a statement of intent at this point in time, unfortunately.

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.
As an additional, @wicket;

If you get further feedback from the mail-lists, IRC channels, or elsewhere that offers a workaround/sol'n to your concerns, please do refine the answer in the doc, or share it here.

Last edited by jalyst; 2013-02-19 at 08:12.
 

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