On 22/07/2009 15:15, Wyllys Ingersoll wrote: > Don Cragun wrote: >> The one-pager for this project says (in section 3.6) that it doesn't >> duplicate core Solaris components. But the description of the Pth >> library provided by this case sure sounds like it is trying to duplicate >> the behavior of the Solaris pthread library and major chunks of basic >> libc functions like read[v] and write[v]. >> >> Why shouldn't this be considered a duplication of the core Solaris POSIX >> threads features even though it adds a "pth_" to the front of a bunch of >> standard function names? >> >> - Don > > > The Pth library is a secondary dependency, so I answered the question with > the main code (GnuPG) in mind. That said, yes it is a bit of duplication. > However, the code will not work without it and because some of the code is > GPLv3, we cannot modify it to remove the dependency.
I don't believe that is true - while GPLv3 may cause legal problems for any thing that uses it (especially if it links with it in any way) - I don't believe that precludes us from modifying GPLv3 code in anyway, especially if you would consider that a porting effort (i.e. using Solaris' pthreads instead of another implementation) - since doing so is using the system libraries, which as I understand (IANAL) it means that it's "safe" to do. 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.
