Re: New icns loading code
Oops, now this all looks like a misunderstanding from my side. Sorry for that I thought that your library was GPL2. The only reason why I had this impression is this web page: http://icns.sourceforge.net/ There you state: libicns is distributed under the GNU public license, Version 2 Perhaps you could detail that statement to stop others from getting the wrong impression. And thank you once more that you took the time to mail us. LGPL 2.1 with a later clause would be perfect. Fred Mathew Eis wrote: Hi all, Just to clarify, libicns is currently already licensed as LGPLv2.1 (See the individual GPL summary in each source file) - the other, and only parts that are GPLv2 or GPLv2+ only are the utility programs, icns2png, png2icns, etc. (I may not be able to get these changed; will that be a problem?) So, I think we are 90% there already. (On which note, is there something in the documentation that indicated the library was not LGPL?) There should be no problem adding the or later clause. Is there some reason to move backwards to the LGPLv2.0 (with the later clause)? My understanding is that there is little difference between the 2.0 and 2.1 versions as far as overall GPL compatability. Take care, -Mathew Eis On Tue, Oct 14, 2008 at 12:35 PM, Fred Kiefer [EMAIL PROTECTED] wrote: Hi Matt, switching to LGPL would be great. For now version 3 is not perfectly usable for GNUstep applications. Some of the more important GNUstep applications are still on GPL2 and this is not compatible with LGPL3. Only for that reason does GNUstep still use LGPL2 or later. If you could use LGPL2 or later as well, we would have a perfect fit here. Cheers Fred PS: Thank you for your great library! Gregory John Casamento wrote: Hi Matt, It's good to hear from you! :) Yes, I think we would like to discuss this. Later, GC Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer - Original Message From: Mathew Eis [EMAIL PROTECTED] To: gnustep-dev@gnu.org Sent: Monday, October 13, 2008 10:00:19 PM Subject: Re: New icns loading code Hi, I just came across your message on the list... I am the primary developer of the libicns code, and also the projects current maintainer. I would hate for you to have to re-do so much work with the icns loading. Would it help if we changed the library's licensing to the LGPLv3? Please CC me in your reply, I am not part of the GnuStep Dev list. -Mathew Eis -snip- Why not just use libicns? It is published with the GPL 2 licence, which may not be suitable for some projects using GNUstep. -/snip- ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: New icns loading code
Hi all, Just to clarify, libicns is currently already licensed as LGPLv2.1 (See the individual GPL summary in each source file) - the other, and only parts that are GPLv2 or GPLv2+ only are the utility programs, icns2png, png2icns, etc. (I may not be able to get these changed; will that be a problem?) So, I think we are 90% there already. (On which note, is there something in the documentation that indicated the library was not LGPL?) There should be no problem adding the or later clause. Is there some reason to move backwards to the LGPLv2.0 (with the later clause)? My understanding is that there is little difference between the 2.0 and 2.1 versions as far as overall GPL compatability. Take care, -Mathew Eis On Tue, Oct 14, 2008 at 12:35 PM, Fred Kiefer [EMAIL PROTECTED] wrote: Hi Matt, switching to LGPL would be great. For now version 3 is not perfectly usable for GNUstep applications. Some of the more important GNUstep applications are still on GPL2 and this is not compatible with LGPL3. Only for that reason does GNUstep still use LGPL2 or later. If you could use LGPL2 or later as well, we would have a perfect fit here. Cheers Fred PS: Thank you for your great library! Gregory John Casamento wrote: Hi Matt, It's good to hear from you! :) Yes, I think we would like to discuss this. Later, GC Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer - Original Message From: Mathew Eis [EMAIL PROTECTED] To: gnustep-dev@gnu.org Sent: Monday, October 13, 2008 10:00:19 PM Subject: Re: New icns loading code Hi, I just came across your message on the list... I am the primary developer of the libicns code, and also the projects current maintainer. I would hate for you to have to re-do so much work with the icns loading. Would it help if we changed the library's licensing to the LGPLv3? Please CC me in your reply, I am not part of the GnuStep Dev list. -Mathew Eis -snip- Why not just use libicns? It is published with the GPL 2 licence, which may not be suitable for some projects using GNUstep. -/snip- ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: New icns loading code
Hi, I just came across your message on the list... I am the primary developer of the libicns code, and also the projects current maintainer. I would hate for you to have to re-do so much work with the icns loading. Would it help if we changed the library's licensing to the LGPLv3? Please CC me in your reply, I am not part of the GnuStep Dev list. -Mathew Eis -snip- Why not just use libicns? It is published with the GPL 2 licence, which may not be suitable for some projects using GNUstep. -/snip- ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: New icns loading code
Hi Matt, It's good to hear from you! :) Yes, I think we would like to discuss this. Later, GC Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer - Original Message From: Mathew Eis [EMAIL PROTECTED] To: gnustep-dev@gnu.org Sent: Monday, October 13, 2008 10:00:19 PM Subject: Re: New icns loading code Hi, I just came across your message on the list... I am the primary developer of the libicns code, and also the projects current maintainer. I would hate for you to have to re-do so much work with the icns loading. Would it help if we changed the library's licensing to the LGPLv3? Please CC me in your reply, I am not part of the GnuStep Dev list. -Mathew Eis -snip- Why not just use libicns? It is published with the GPL 2 licence, which may not be suitable for some projects using GNUstep. -/snip- ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: New icns loading code
Hi Matt, switching to LGPL would be great. For now version 3 is not perfectly usable for GNUstep applications. Some of the more important GNUstep applications are still on GPL2 and this is not compatible with LGPL3. Only for that reason does GNUstep still use LGPL2 or later. If you could use LGPL2 or later as well, we would have a perfect fit here. Cheers Fred PS: Thank you for your great library! Gregory John Casamento wrote: Hi Matt, It's good to hear from you! :) Yes, I think we would like to discuss this. Later, GC Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer - Original Message From: Mathew Eis [EMAIL PROTECTED] To: gnustep-dev@gnu.org Sent: Monday, October 13, 2008 10:00:19 PM Subject: Re: New icns loading code Hi, I just came across your message on the list... I am the primary developer of the libicns code, and also the projects current maintainer. I would hate for you to have to re-do so much work with the icns loading. Would it help if we changed the library's licensing to the LGPLv3? Please CC me in your reply, I am not part of the GnuStep Dev list. -Mathew Eis -snip- Why not just use libicns? It is published with the GPL 2 licence, which may not be suitable for some projects using GNUstep. -/snip- ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: New icns loading code
I had to make one minor fix, but otherwise it works fine. Thanks. GC Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer - Original Message From: Fred Kiefer [EMAIL PROTECTED] To: GNUstep Developer gnustep-dev@gnu.org Sent: Wednesday, September 3, 2008 3:46:30 AM Subject: New icns loading code I just committed a change to gui that adds some basic icns loading even when libicns is not present on a system. Even with that code in place libicns will be the better solution in many case. Why not just use libicns? - It is published with the GPL 2 licence, which may not be suitable for some projects using GNUstep. - It is currently not shipped with my Linux distribution. My implementation has been done without looking at the libicns code, just by following there documentation and Gregs usage of their functions. I also added some ideas found in Nikolaus Schallers myStep implementation of icns loading. The code I added has many limitations, which are probably not even worth fixing, as we should be using libicns for the more complex cases. There are also a few bugs (something that looks like an of by one case for 128 bit images), these surely need fixing. I also changes Gregs loading code a bit, as it was leaking memory and could not load any icns file that didn't have a 48x48 representation. Somebody needs to check that this still works with libicns. Fred ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
