> > I think it is suitable, because: > > 1) It prevents other compiler vendors from incorporating SDCC code in their > > proprietary products. > > 2) It places no restriction in distributing the compiled executable > > 3) It serves the same role in gcc as libsdcc in SDCC. > > It is the GPL with linkage exception.
OK, now that I know it, GPL with linkage exception seems to be pretty perfect. Given that we somehow agree on one license, how to proceed from there? Should "every" library maintainer check his/her own files (from ChangeLog/svn annotate entries/file contents for contributors and authors, contact them by mail, and ask them for permission to update the libraries' licence? Or can we reduce the effort by stating that only registered developers can have contributed, limiting the scope of required "Fine with me" mails? Will a mail in the sdcc-devel list (such as this one ;-)) be enough or do we need to ask irresponsive developers explicitly via mail? I can check the PIC14/PIC16 libraries (should not be too difficult, except for files just copied over from device/lib) and mail the contributors... if that's the way to go. Should we set up a Wiki page with votes for this or that license, agreements from all developers, ... to coordinate this action? -- Regards, Raphael Neider Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
