In article <[EMAIL PROTECTED]> you wrote:
> I've been subscribed to this list for several weeks now, and have seen no > indication that someone is actually maintaining pth. There have been at > least 4 bug reports, 3 of which included fixes. I'd like to know if > someone is keeping track of all the fixes people are providing, since I > recently added pth support to a piece of software I wrote. Pth is both part of the GNU and the OSSP project (where it is physically located and developed). Unfortunately it seems that I've written too much software over the last years ;), because there are lots of packages which I no longer seem to be able to update as fast as people expect it. Sorry, but I can do only as much as my time permits. Pth is definetely maintained by me and the OSSP project team (especially because it is an essential part of OSSP), but it is right that active development slowed down in the Pth area and that official releases occur less frequently. That is mostly because we are focusing currently on other parts of OSSP (see http://cvs.ossp.org/timeline) and Pth already works fine for us so far. But if you look at http://cvs.ossp.org/pkg/lib/pth/ChangeLog and the CVS files at http://cvs.ossp.org/pkg/lib/pth/ you will see that we're working on Pth and updating it, too. Additionally we have many prepared or contributed patches in the development queue, but most of them cannot be directly applied because they are either partly unfinished or not 100% correct. For instance look at the thread "Bug in pth_connect_ev" and the attached patch pth-1.4.1-nonblock.asp.patch: sure, one can say "hey, there are patches posted, but not included into Pth". But if you look closer you will see that it would be not reasonable to include them as is. Sure, this could be communicated better by us. Sorry for this. So, sorry for not beeing able to communicating with you as expected. But do not treat this like we are not interested or do not maintain Pth. We try our best with the OSSP project, but obviously we cannot focus all the time on all sub-projects. If you look at http://cvs.ossp.org/timeline regularily you will notice that we're very actively developing inside OSSP. Although, as explained, currently not in the Pth area. But this changes back and forth on demand. In case there are still any problems and/or patches around we still have not included into the CVS state of Pth (see http://cvs.ossp.org/pkg/lib/pth/), please do not hesitate to repost them here again. Perhaps they were just lost or overlooked. I'll try to make sure they are considered again. Finally, please notice that the following three URLs point you all the time to the physical home of GNU Pth, because it is a sub-project of the larger OSSP project: o http://www.ossp.org/pkg/lib/pth/ o http://cvs.ossp.org/pkg/lib/pth/ o ftp://ftp.ossp.org/pkg/lib/pth/ The GNU URLs.. o http://www.gnu.org/software/pth/ o ftp://ftp.gnu.org/gnu/pth/ ...are just copies of the OSSP data. Yours, Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ GNU Portable Threads (Pth) http://www.gnu.org/software/pth/ User Support Mailing List [EMAIL PROTECTED] Automated List Manager (Majordomo) [EMAIL PROTECTED]
