On Mon, Dec 15, 2014 at 09:27:48AM +0100, Martin Gräßlin wrote: > > Baloo is still LGPL, when you aggregate it current Xapian code the result > > becomes GPL, but I could write something different with the same header > > interface as Xapian and make it LGPL, and then the aggregation would be > > LGPL. (Or maybe not, not sure what was the result on that lawsuit saying > > that APIs were copyrightable or not, i guess we could always white-room it > > :D) > > > > Does what am I saying make any kind of sense? > > I think Jonathan should respond to it. Your argumentation makes sense to me, > but the question is whether Baloo is currently derived work of Xapian or not. > If there is baloo internal an abstraction allowing to easily swap out Xapian > by something different I would say it's not derived work. But if Xapian is > deeply wired into Baloo I would say it's derived work.
Albert is right, Baloo is LGPL but the resulting binaries will be GPL. As long as we are all happy with that and we make it clear with a big README in the source we're good to go ahead. Jonathan _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
