Darren Kenny wrote: ... > > The main concern is that the code changes you make, must be published (which > most code is right now) - a patch should be fine - and all the better if you > could push that patch upstream to the GnuPG maintainers. > > What makes you think that modifying GPLv3 code is not possible? > > Darren.
Pth is actually LGPL v2.1, sorry for the confusion. GnuPG is GPLv3. When I filed the OSR for the case, I was instructed (by the lawyers) that I needed to check the box that says "As a stand alone distribution* of open source technology." and NOT the box that says: "As a stand alone distribution* of open source technology which may include Minor Contributions back to the same third party open source project from which the open source technology is being licensed. "Minor contributions" include minimal changes to the open source technology such as porting, bug fixes, or compatibility testing. These changes must be newly created by Sun or Sun employees, and may NOT include pre-existing Sun technology or new functionality." However, the issue is really around the modifications to GnuPG itself, which IS GPLv3. Specifically, the gpg-agent and gpg-connect-agent utilities that are part of the GnuPG package. While it *may* be permissible to apply patches to that code to get rid of the Pth dependency, I don't see the benefit other than to say "Look, it uses Sun native threads!". If someone wants to go to the effort of creating the patches so that it compiles on Solaris using pthreads or Solaris threads instead of Pth, they could contribute that to the upstream GnuPG community and we could catch it later in a resync/update, but I don't think it should be a goal or requirement for this project. We want to integrate with as few changes as possible against the original packages. -Wyllys
