Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!j.cc.purdue.edu!rsk
From: rsk@j.cc.purdue.edu.UUCP
Newsgroups: comp.sources.d
Subject: Re: Software Obsolescence
Message-ID: <3735@j.cc.purdue.edu>
Date: Wed, 1-Apr-87 11:46:39 EST
Article-I.D.: j.3735
Posted: Wed Apr  1 11:46:39 1987
Date-Received: Sat, 4-Apr-87 06:45:38 EST
References: <272@unixprt.UUCP>
Reply-To: rsk@j.cc.purdue.edu.UUCP (Wombat)
Organization: Purdue University Computing Center
Lines: 25
Keywords: News 2.11 Patch
Summary: Revisions != Obsolesence

In article <272@unixprt.UUCP> cody@unixprt.UUCP (Commando Cody) writes:
>I have been following the distributions and patches for both news 2.11
>and Patch. Both have accumulated 5 or more lengthy patch files.
>Considering the importance of both programs to the USENET community,
>isn't time for a revised posting of both with all current, official
>patches folded in.
>
>A new clean base for distribution appears highly desirable.

I strongly disagree.  Given the base distribution for news 2.11 and
the patch files, and "patch" itself, it takes less than an hour to
completely patch and regenerate news 2.11 on a Vax.  I think it would
be tremendous waste of Usenet resources to repost the entire 2.11 sources.
Given the ease of generating a completely up-to-date news 2.11 from
the original sources and the patches, what's the problem?

Note that rn release 4.3 is at patchlevel 39, and I've had no trouble t'all
getting it to that level by simply tracking Larry Wall's released patches.

Internet sites are welcome to anonymous-ftp news, rn, nntp, and some
other items from this machine (j.cc.purdue.edu); the versions available
through ftp tend to track the revisions as they are locally applied.

Rich Kulawiec, rsk@j.cc.purdue.edu, j.cc.purdue.edu!rsk
PUCC News Administrator