That's fine. I am not planning on making changes to PEL classes, I just want to include them with my application. I only use pel to extract EXIF tags, currently not even changing any tags in the image.
I will just include the PEL folder with my package then. Later I plan on setting up a pear channel and use PEAR installer, then I will also set it up to install PEL as one of the dependencies. Martin Geisler wrote: >Dmitri <[EMAIL PROTECTED]> writes: > >Hi Dmitri > > > >>This is whay I found on a website: >> >>quote: >> When we say that GPLv2 and GPLv3 are incompatible, it means there is >> no legal way to combine code under GPLv2 with code under GPLv3 in a >> single program. This is because both GPLv2 and GPLv3 are copyleft >> licenses: each of them says, “If you include code under this license >> in a larger program, the larger program must be under this license >> too.” >> >> > >Yes, that is correct -- but only if the code is GPLv2-only. PEL is >GPLv2-or-later which means that you can combine it with freely with >GPLv3 code. By doing so, you change the license from GPLv2-or-later to >GPLv3 on your copy of PEL. > >That is fine! If you make some cool changes to PEL, then those changes >will be GPLv3 licensed. If I want to include them in PEL, then I'll have >to switch my master version of PEL to GPLv3 too. I guess I'll do that in >time anyway :-) > > > >>I wonder what is the best way for me to make use of PEL in my project? >>The easiest way for the end-user would be if I just include a folder >>'PEL' in my application and then require classes from PEL when needed. >>But I am not sure if I can do it now because all other code in my >>project in under GPL v2? >> >> > >Yes, I really believe you can include PEL with no problems. > > > >>The other way is to instruct the user to download and unpack the PEL >>themselves somewhere on their system and then add that directory to >>include path. This will not violate any incompatability with 2 GPL >>licensed but a little 'less easy' for the end user. >> >>Any thoughts on this? >> >>PS. if you upgrade to GPL 3, then projects that are under GPL 2 will >>have the same issue as I'm having now. >> >> > >Yeah, I believe this is the only problem in upgrading PEL... If anybody >have GPLv2-only that include PEL, then upgrading to GPLv3 would mean >that they cannot upgrade to the newer GPLv3 versions. They would of >course still be able to use the current GPLv2-or-later PEL version. > > > -- Open Source ALL content management with streaming video http://wiki.sharedlog.com ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ PEL-devel mailing list PEL-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pel-devel
