Path: utzoo!attcan!uunet!convex!killer!bigtex!james
From: james@bigtex.uucp (James Van Artsdalen)
Newsgroups: comp.sources.d
Subject: Re: PATCH usage
Message-ID: <3046@bigtex.uucp>
Date: 30 Jun 88 22:49:51 GMT
References: <393@sce.UUCP>
Reply-To: james@bigtex.UUCP (James Van Artsdalen)
Organization: F.B.N. Software, Austin TX
Lines: 30

IN article <393@sce.UUCP>, graham@sce.UUCP (Doug Graham) wrote:
>     In a similar vein, I noticed that when "perl" first appeared
> on the net, it was immediately followed by a large number of
> patches. (Around 25 I think) Since these patches came so close
> on the heels of the original source, it seems to me that they
> must have been available when the original source was posted.
> Why were they not applied before the source was posted?

When a program is sent to comp.sources.unix, it isn't instantly posted
to the entire net.  If nothing else, Rich $alz has an employer who
doesn't pay him to handle net sources...  Also, I get the impression
Rich makes an effort to ensure that (1) junk doesn't get out and (2)
that sources will unpack correctly, do have man pages, and all that
stuff.  It clearly takes a lot of time.

When Larry sends in sources, he usually (always?) makes it available
via ftp at the same time, so that people with arpanet connections can
get the sources without waiting for the comp.sources.unix postings.
Those people then start compiling & using *and sending in bug reports*
before the sources are actually posted.  Thus it is possible that bugs
would be fixed fairly quickly, before the sources made it out.
Recalling the sources from Rich would just delay the real release
indefinitely: there are *always* more bugs.

I have perl & the other programs from devvax.jpl.nasa.gov available on
bigtex for anonymous uucp download via TB+ if there's anybody who
can't wait.
-- 
James R. Van Artsdalen   ...!ut-sally!utastro!bigtex!james   "Live Free or Die"
Home: 512-346-2444 Work: 328-0282; 110 Wild Basin Rd. Ste #230, Austin TX 78746