Path: utzoo!utgpu!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.BFM.COM (Tom Neff)
Newsgroups: alt.sources.d
Subject: Re: Perl patches (was Re: shar 3.49 (part 2 of 2))
Message-ID: <15865@bfmny0.BFM.COM>
Date: 21 Sep 90 01:51:28 GMT
References: <1990Sep16.170917.11901@lokkur.dexter.mi.us> <727@array.UUCP> <1990Sep21.020331.2225@zorch.SF-Bay.ORG>
Reply-To: tneff@bfmny0.BFM.COM (Tom Neff)
Lines: 25

In article <1990Sep21.020331.2225@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes:
>As for why it was such a particular irritation to me, my host site was
>a school system, perennially short for space, so I'd download perl to
>my home system (tedious in the extreme on a slow modem), delete it from
>the host site, and Boom! -- another patch.  Since no "patch" was available
>for my home system in those days, _upload_ perl, _patch_ perl, _download_
>perl, _delete_ perl on the host, iterate 25 more times.
>
>Folks releasing things in dribbles don't realize the byzantine transport
>mechanisms and tool compromises some of their audience has to suffer
>to accomodate their habit,

All this means is that if you want to be part of an ongoing development
project like Perl, don't do it on a tinkertoy setup where patching is a
terribly laborious process.  If you must use such a setup, wait a few
patches before rebuilding, or ignore the whole thing until a stable
version is released.

There are plenty of people whose systems accomodate new patches in a
matter of minutes.  Leave the intensive development cycle to them.  Mere
"patch envy" is a user problem.

-- 
Nobody wants justice.   /\ \/   Tom Neff
   -- Alan Dershowitz   /\ \/   tneff@bfmny0.BFM.COM