On 17 Sep 2007, at 20:51, Yen-Ju Chen wrote: > MenuServer (Saso) is GPL 2, but the ETMachineInfo_FreeBSD.m > (David) is in BSD. > (I am not sure it is allowed in this case).
All of the ETMachineInfo_* bits are 3-clause BSDL except the Linux version, which is GPLv2, since I based it on Saso's code. The class and the other implementations were written independently of MenuServer and then integrated (I got Nicolas to put them in svn), so they are not derived works of MenuServer (except, as stated, the Linux backend). I think the best idea is to pull the power management code out of ETMachineInfo and put it into a separate class / category in SystemConfig. When Quentin suggested putting ETMachineInfo into EtoileFoundation, I'd forgotten that the Linux code was GPL'd (which won't work in EtoileFoundation, since GPLv2 is incompatible with ASLv2 [1]). This is not a problem if Saso is happy with relicensing the code under a BSDL, however. > SystemConfig (Quentin and Guenther) is under LGPL2. > I understand everyone has his opinions on the license. > I *personally* think the easiest solution is to turn SystemConfig > into BSD. > Comments ? You can put BSDL code in an LGPL project, so it's not a huge problem. I'd prefer BSDL, but I don't have any strong objections to LGPL (is it v2, or v2-or-later?). If Quentin and Guenther are happy with relicensing SystemConfig, then that's great. If not, then can we keep the BSDL code in a subframework, so that it's clear to people which bits are LGPL and which are BSDL? David [1] Lawyers. Can't live with 'em, can't fit 'em all in the 'B' Ark. _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
