Xref: utzoo news.software.nntp:942 news.software.b:6240 comp.sources.bugs:2672
Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!bcm!lib!lib.tmc.edu
From: rrn@lib.tmc.edu (Stan Barber)
Newsgroups: news.software.nntp,news.software.b,comp.sources.bugs
Subject: Comments on continuing to provide support for RN/RRN
Message-ID: <4365@lib.tmc.edu>
Date: 26 Nov 90 05:13:49 GMT
Sender: sob@lib.tmc.edu
Followup-To: poster
Organization: Houston Acacdemy of Medicine/Texas Medical Center Library
Lines: 28

If you are having problems with Patch 50 and ndir.c, please use the
version just posted to these groups. That should address the problem.

I am debating on continuing to post patches to rn/rrn. It seems I always
run into a case where the patch fails on someone's version of rn/rrn.
While I am sure it is very frustrating to have this happen to your copy,
imagine being on the receiving end of all that frustration mail.

This is why I have always provided full kits available via anonymous ftp
whenever I have done a patch. That way, you can have exactly what I have.
Now, I know this is not a complete answer for those of you not on the internet.
However, there are anonymous uucp sites around that provide them. I have
also thought of building a specific archive-server just for rn/rn and nntp
so people could avoid the frustration of having the patches fail. Such a 
server will come on line by the end of the year mostly to deal with nntp
requests.

The future of rn/rrn is uncertain. With the success of trn, there may be
no need to continue to maintain rn/rrn. Then again, they may merge. This
is largely Wayne Davidson's decision. Hopefully, he will be well enough
soon to share his views with me on these issues. [Note: He was in an
auto accident recently.]

I am sure the blame is mine for all these problems. I appologize for any
frustration I may have caused you.

Your comments on these matters are welcome. Please use the "rrn@lib.tmc.edu"
address.