To view parent comment, click here.
To read all comments associated with this story, please click here.
Actually Qt fullfills the licence criteria as it is available under an open source licence and does not prohibit proprietary usage.
The "problem" comes from the shift of goals inside the LSB.
While it has been a goal to define a standard set of libraries software vendors could rely on when installing their software, they now aim at providing an as-cheap-as-possible development environment.
But there is still the possibility that thee LSB's goals will get back to making software deployment easy.
Only time will tell
Actually Qt fullfills the licence criteria as it is available under an open source licence and does not prohibit proprietary usage.
As http://www.linuxbase.org/futures/ideas/issues/libqt/ explains, LSB considers charging a license fee for commercial use `prohibitive'. All things considered, I think that's pretty reasonable.






Member since:
2005-06-29
Actually, the LSB is about having free software base, so the FSF/Stallman are very relevant.
Nope, that is not what the LSB is about. This is what the LSB is about.
From http://freestandards.org/pipermail/lsb-futures/2005-March/001489.ht...
"The LSB license criteria currently states,
The component should have at least one compliant implementation
available under an Open Source license that also promotes a "No
Strings Attached" environment for developers. This means that the
developer would be able to develop and deploy their software however
they choose using at least one standard implementation. This is
interpreted to mean that at least one implementation is available
under a license that meets the Open Source Definition but it does not
prohibit propriatry usage. The rationale for this criteria is very
similar to that of the LGPL."