El dl 01 de 02 de 2010 a les 14:25 +0000, en/na Barry Haddow va escriure: > > The LGPL means you can link with proprietary code. The GPL does not > > allow this. If you use GPL software in your application it means you are > > obliged to share your changes with the developer community, the LGPL > > allows you to link with other code, but if you change the LGPL code I > > believe you are still obliged to share your changes. > > > > Hi > > I think this is a bit misleading. Suppose I make some modifications to moses, > or any other GPL/LGPL piece of software. If I don't give the executable to > anyone, then I don't have to give them the source code either. There is no > obligation to 'share my changes to the developer community' > > See here: > http://www.gnu.org/licenses/gpl-faq.html#NoDistributionRequirements > http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic > > You can also link with GPL software, and use it in your application > (internally). The GPL only swings into action if you redistribute this > application, > > > So for the original poster, it's possible to you moses internally, without > charge. It's also possible to redistribute copies of moses, as long as you > retain the original license. If you distribute modified versions of moses to > the public, then you *must* make the source code of those modifications > available. You can distribute a proprietary application which links with the > moses library (since this library is LGPL) but not with randlm (since it's > GPL).
A much better explanation, thanks! Fran _______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
