Xref: utzoo alt.sources.d:1253 comp.sources.d:6223
Path: utzoo!utgpu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)
Newsgroups: alt.sources.d,comp.sources.d
Subject: Re: Read this if you're having trouble unpacking Tcl
Message-ID: <1990Dec29.031708.29309@NCoast.ORG>
Date: 29 Dec 90 03:17:08 GMT
References: <7372@sugar.hackercorp.com> <88817429@bfmny0.BFM.COM> <1990Dec27.071632.7272@zorch.SF-Bay.ORG>
Reply-To: allbery@ncoast.ORG.ORG (Brandon S. Allbery KB8JRR)
Followup-To: alt.sources.d
Distribution: alt
Organization: North Coast Computer Resources (ncoast)
Lines: 44

As quoted from <1990Dec27.071632.7272@zorch.SF-Bay.ORG> by xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan):
+---------------
| tneff@bfmny0.BFM.COM (Tom Neff) writes:
| > karl@sugar.hackercorp.com (Karl Lehenbauer) writes:
| >>Enclosed is the help file for anyone who is having trouble unpacking Tcl.
| >If people would just post source to the source newsgroups, instead of
| >this unreadable binary crap, no help file would be necessary.
| 
| I don't think complaining about the packaging is fair if the product
| arrives intact because of it, but Karl's choice of cpio over tar was
| unfortunate. At any rate, as he indicated in his posting, the
| comp.sources.unix archive pax, in volume 17, does indeed allow
| compilation of a cpio (clone?) that successfully unpacks tcl; I just
| finished doing just that.
+---------------

There's also afio.  Also, since you're so hip on getting savings, cpio doesn't
waste space making sure everything is on a 512-byte boundary.  (In a large
archive, this *can* make a difference.)

+---------------
| Remember, almost nowhere on the net do the *.sources.* files arrive
| without having been compressed somewhere along the way; seeing them
| delivered to you in a compressed format merely defers the final
| unpacking to you, at some cost in convenience but benefit in size and
| robustness of transport. No one was going to eyeball that whole
+---------------

No benefit in size, I fear.  Compress in a pipeline can't do its usual sanity
checks; "compress file; uuencode file.Z file.Z | compress > file.uu.Z" actually
results in file.uu.Z being considerably larger than file.Z, because an already-
compressed file *expands* and uuencode also expands the file somewhat (but
doesn't make it compressable again).  Compressed uuencodes actually waste
considerable space/time.

I suspect that the only real solution to "robustness" issues will be X.400 or
an equivalent.

++Brandon
-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY