On Monday, 2013-08-12, Ryan Bramantya wrote: > I think there is no need to use tri-license. Based on LGPL licensing > policy, it said that LGPL can be converted to GPL (but not vice versa).
It doesn't have to be converted, it is compatible. > Therefore, by chosing LGPL as license, if someone want to create GPL > software, the just converting it to GPL and if some one want to create BSD > or proprietary software and avoid LGPL, the just dynamically linking their > software to LGPL component which wouldn't affect their BSD or proprietary > license. This is what I see as the advantage of LGPL from any other > license. Which is why libraries are usually LGPL licensed. Can you give an example where one would want to use application code to create a new library and link against it when the original source of the code is not using said library? Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
