[Kde-pim] Possible solution.

[Allen Winter]

On Sunday 24 June 2007 5:27:15 pm Tobias Koenig wrote:
> On Sun, Jun 24, 2007 at 09:29:08PM +0200, Ingo Klöcker wrote:
> > On Sunday 24 June 2007 20:55, Tom Albers wrote:
> Hi Ingo,
> 
> > > how about puting it in a 'gpl' subfolder? It's less ugly as creating
> > > a kdepimlibs-gpl and a better than dropping the LGPG requirement.
> > 
> > I object. We should have a strict separation between GPL and LGPL code 
> > in order to avoid
> > - accidentally using GPL code in LGPL code
> > - accidentally moving code from the gpl subfolder to another file
> > - anyone accidentally using GPL code for proprietary software 
> > development
> Since we (the KDEPIM developer) are the only guys which work in
> kdepimlibs and Allan always have an eye on his baby I think such a mixed
> usage you mentioned won't happen.
> 
> We just have to make sure that the developers which are using the
> libraries know about the separation. So the header files should include the
> correct licence header and the libxyz could contain '-gpl' in the name.
> 
> If somebody is using GPL code in a propritary software we can always ask
> him kindly to change his dependency.
> 
Tobias,

So, if I understand correctly, you second toma's kdepimlibs/gpl subdir proposal?
And we rename all the installed headers to foo-gpl.h?  And the installed library as libfoo-gpl.so?

Just want to be clear. 

Having yet-another-module "kdepimlibs-gpl" isn't very appealing.

-Allen

_______________________________________________
kde-pim mailing list
kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/