On Mon, Nov 03, 2008 at 11:32:59PM +0100, JMD wrote: > Hi Pierre, Hi,
> > This would prevent distributing GLPI as free software (since it can, in > > some cases, prevent derivative works from being distributed). > > Perhaps but the author say in the new version of the lib : "you may > distribute the resulting work only under a license identical to this one > (Can be included in GPL/LGPL projects)" > > http://alexandre.alapetite.net/doc-alex/domxml-php4-php5/domxml-php4-to-php5.php.txt > > I don't know if it's ok for debian or not. Hm, the author has stated 'under a license identical to this one', which is quite useless for us (the only identical license is .. the same ;). I *suppose* he wanted to say equivalent (in terms of free software), but I can't speak for him. The real solution would be to use a double license, for ex. 'at you convenience use CC-SA 2.0 or GPL version x', but only the author can decide that. Allowing GPL license would allow commercial derivative works (if GPL, of course). I'm adding him to the CC list. [...] > > As I am not sure how exactly it would affect GLPI, I'm asking for > > advice: can I safely remove phpCAS from GLPI archive distributed in > > Debian ? > > If you see any better solution, please also tell me. > > First, do you need a urgent answer ? Which GLPI release do you want to > package now ? As soon as possible ;) I need to patch all versions included in Debian > > Differents workarounds : > > - Put the new lib in the package if the licence is ok > > - Remove the lib from the package and put a README to explain that the > user must download the lib himself. > That is the most probable solution, if Alexandre keeps the license in the current state. I'll wait for a few more days for his reply. Cheers, Pierre _______________________________________________ Glpi-user mailing list [email protected] https://mail.gna.org/listinfo/glpi-user
