(forgot AUTHORS in cc list) PLEASE REPLY (authors on CC list). yes or no to adding static linking exception below?
On Fri, 17 Oct 2008 00:53:29 +0200 Michael Feiri <[EMAIL PROTECTED]> babbled: this got debated to hell. the alternative was going to be watching developers leave - ones wanting to add in better code but only wanting to do so if they know their code will be free and improvements to it given back. if we added the static linking exception - which imho would not violate the spirit of the LGPL, would this be good enough? (nb - if apple decide to place all these nasty nasty nasty restrictions on developers and applications - all the best to them, but i know i have zero interest in becoming part of that world as long as apple basically say "you do just what we say, what we want, and if we don't like you we'll just ban your app from the platform because you may possibly compete with us or be the wrong shade of pink for steve jobs"). i definitely buy the ecos (static linking) argument. i've explicitly cc'd all the AUTHORS for eina. do you guys agree to adding an ecos-style static linking exception (here it is for you guys): "...As a special exception, if other files instantiate templates or use macros or inline functions from this file, or you compile this file and link it with other works to produce a work based on this file, this file does not by itself cause the resulting work to be covered by the GNU General Public License. However the source code for this file must still be made available in accordance with section (3) of the GNU General Public License. This exception does not invalidate any other reasons why a work based on this file might be covered by the GNU General Public License...." > On monday, starting with revision 36622, all vital EFL components have > been configured to depend on copylefted code (eina is licensed under > LGPLv2.1). This is unfortunate, as it renders the existing BSD-style > license agreement essentially worthless. It is especially unfortunate as > the EFL seems to be unique as the only successful GUI environment under > a BSD-style license. > > I have used Evas as a component in a proof-of-concept for an embedded > project using the eCos operating system. No patches or other information > have been published yet, because the project is not yet released. But I > do expect to have patches for EFL ready upon release in order to avoid > the advertisement clause. > > Now, eCos is owned by the FSF and is licensed under the GPLv2 with a > linking exception that makes it completely non-viral. This exception is > more powerful than the LGPL, because the LGPL does require dynamic > linking or the distribution of linkable object files and additional > modification and reverse engineering rights. These obligations would > "infect" a project that would otherwise just use a non-viral GPLv2 with > linker exception. > > So I want to ask you to please consider keeping the core EFL components > and non-optional dependencies under the existing BSD-style license or > consider a non-viral copyleft like the GPLv2 with a linking exception in > oder to keep the EFL usable with eCos and similar free embedded > operating systems (FreeRTOS and RTEMS both use GPLv2 with linking > exceptions too). Dynamic linking is not an option for deeply embedded > operating systems. Often we dont even have a filesystem. > > Additionally I might mention that the BSD-style license of the EFL could > mean that the EFL might technically be the only serious option for a > free 3rd party GUI library on things like the iPhone. Dynamic linking > does seem to exist on this platform but things like forced codesigning, > bans on externally loadable code, and restrictions on reverse > engineering and modification rights make the use of copylefted code > "questionable" at best. > > MfG, Michael > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
