On Fri, 18 Jan 2013 02:48:23 +1000 David Seikel <onef...@gmail.com> said:
> On Thu, 17 Jan 2013 14:12:29 -0200 Gustavo Sverzut Barbieri > <barbi...@profusion.mobi> wrote: > > > On Thu, Jan 17, 2013 at 1:36 AM, David Seikel <onef...@gmail.com> > > wrote: > > >> Well, the resulting license is different. Indeed it will be LGPL. > > >> But say you take Evas and remove eina dep, you could use that as > > >> BSD. > > <snip> > > > There is nothing related to virus other than FUD > > You said so yourself, the BSD licensed parts of EFL are now effectively > LGPL licensed. That's not FUD, that's viral. > > > BSD says nothing other than you must retain its copyright when you > > distribute its source code. It's fully a subset of LGPL, as so LGPL is > > more restrictive, extending with more clauses. > > BSD does not say anything about restricting the right to copy in the > way LGPL does. It's a copyright licence, as such, it reflects the > desires of the copyright owner and is a legal document. A third party > is not allowed to further restrict those copyrights, they simply do > not have that right. It's legal rights, not code, we don't get to > refactor things to our liking like that. lol you could argue then that your placing a restriction of "you pay me and then you get this code" is violating bsd. stop violating it you evil man! copyright is absolute ownership. no one has a right to copy copyrighted work EXCEPT if given permission by the copyright owner. the license is granting people such permissions... given you adhere to certain conditions. the conditions bsd gives are few and far between... and so you are free to ADD restrictions on top as it does not forbid them and so long as they do not conflict with the minimal conditions it already has set. LGPL and even GPL do not interfere with those conditions. seriously - read up on some legal opinions here. we can debate this virus thing all u like but its pointless. if we dont allow lgpl many devs wont contribute. as gustavo said - we cant sensibly relicense lgpl->bsd. we are respecting the wishes of the developers doing the contribution. for sanity we have had to limit the license per lib to "stick to the license of this lib please so it doesn't become "file x has license a, file y license b etc.". except for a few "contained" exceptions (epp, small). your ranting about lgpl being viral is totally uninformed. it's FUD spreading. lgpl clearly defines a limited container for its license - and that is the shared library binary that is produced (in the simplest form - it goes on to define how this boundary looks. gpl (for libs) is viral. bsd requires you (and thus also your clients) to adhere to its demands. that is to reproduce that copyright notice. lgpl simply adds that they ALSO produce the source for that library too alongside the copyright notice, including any changes made to it - ie the EXACT source used to build the binaries they use. it also pretty much asks them to not statically compile the library into their binaries (be they other libraries or just executables). WE in the efl world ALSO pretty much say the same even of bsd libs - dont statically compile please. we USE library file locations that we derive FROM the binary that owns the symbols of evas, eina, edje etc. to FIND things like data files, modules etc. so we push towards this for technical reasons - and there is nothing incompatible or bad about lgpl pushing towards the same goal effectively. maybe you should explain it this way - lgpl is just these simplified extensions on bsd - attach the exact src used to produce that shared lib along with the already required license/copyright notice AND don't statically link. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
