On 5/2/2011 9:56 AM, Attila Csipa wrote:
On Monday 02 May 2011 16:50:32 you wrote:
the tools are there to help you make sure your bugfixes didn't
accidentally break things. They're not there to be watertight against
breaking the compliance rules by someone who wants to cheat the rules.
One thing though - the original question was if you can *switch* licenses, and
that situation is pretty clear. However, is there anything that would prevent
you from having two sets of Qt libraries, on one side the stock LGPL ones, and
a parallel set of packages, which would be the commercially licensed one (in a
separate path, no dependency relations to the LGPL libs, etc), which you could
use/customize for whatever you want to do with it within your blend of MeeGo,
without affecting compliancy and/or compatibility ?
as long as apps that get installed get the system one... and only one
app gets yours;
but at that point... what's the reason for an OS vendor to do this
(an App vendor can install his own library in an own path obviously)
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
