Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!rex!ames!uakari.primate.wisc.edu!xanth!xanth.cs.odu.edu!tadguy From: tadguy@cs.odu.edu (Tad Guy) Newsgroups: comp.sys.amiga Subject: Re: csa & cba postings Message-ID: Date: 20 Jan 90 02:23:09 GMT References: <75826@tut.cis.ohio-state.edu> <9001181640.AA03664@sorinc.UUCP> Sender: news@cs.odu.edu Followup-To: comp.sys.amiga Organization: Old Dominion University, Norfolk, VA Lines: 88 In-reply-to: magik@sorinc.UUCP's message of 18 Jan 90 17:40:20 GMT The impatient should search forward for ^------ to see a summary and something that should make many happy... ...tad swan@jolnet.ORPK.IL.US (Joel Swan) writes: >>>>>The recent "ChatterBox" posting will not "unshar" correctly, >>>>>because it uses filenames longer than 14 characters. > >Besides, why make LONG, hard to tyoe names like "chatterbox.zuu01" instead >of "chatb.zuu01"? Because it's the name the author used? It's easiest for me to not change things when possible. Not only does it make the submissions go out faster, but it saves me the aggravation.. Why type the names at all? Real UNIX weenies use * and ? and wouldn't type a file name longer than a few characters anyway (and some of us are addicted to file name completion). :-) >Tad, please consider a limit to name size. It won't really limit you >that much -- but it sure will help many of us a lot. Until your posting (and a private message I had received today), I was under the impression the complaint was with the names of the files in the sources shars, not the names of the split uuencoded files (in looking back at the articles I see nowhere where this was made clear). Since I am generating those intermediate names, it's reasonable for me to keep them down to 14 characters in length (in fact, I have already modified my posting script to force me to rename .zoo files down to 12 characters in length, to allow for the part number). Previously I had only been concered with the length of the names of the Archive-name: secondary header... So, the intermediate uuencoded files will now be within 14 characters in length. However, I will not change the names of the files in the sources shars. There's no way I could do it and not break a majority of the sources, since I will miss something in trying (not to mention the major slowdown this would cause). magik@sorinc.UUCP (Darrin A. Hyrup) writes: > I think what Tad should be doing is to post all submissions as .ZUU > files (uuencoded ZOO files, broken up into whatever file sizes > chosen). That method allows those who unarchive their files on UNIX > (or any OS) to uudecode the files, and put them together into a .ZOO > file that can easily be transported to wherever it need go. No can do -- one of the ``rules'' about the sources groups is that the sources posted must be in a plain-text form (shars qualify). Encoding them into zoo's would not be appreciated by the backbone cabal (even including uuencoded binaries isn't really legit). Sources must remain readable without unusual software... > Plus that also makes it easier to handle submitted binary files and > object code (besides having obvious storage and transfer time > savings over uncompressed shar files.) You're real close to proposing to get rid of the sources group and going only with the binaries group. It'd make things easier for me, but I don't think it would pass a vote. I know I woudn't vote for it, and I think you'd find it'd meet with opposition from those without Amiga who want to browse the sources postings... > (Although my personal preference would be to have uuencoded LHARC > .LZH files instead of .ZOO files to conserve net bandwidth and save > transfer times.) I have no UNIX LHARC, and I will not download everything to my Amiga just to package it. Zoo remains the most widespread archiver available. (I often wish no one had made an Amiga LHARC until after an UNIX version came out). ------ I think that covers everything: 1. The foo.zuuxx files are now limited to 14 characters. 2. The filenames in sources postings remain unchanged. 3. The sources must remain plain-text. 4. LHARC is out of the question until I get a UNIX version. Oh, and an Amiga UNSHAR program that reads the sources and binaries postings (as well as those of comp.sources.misc, at least) is in my queue and will go out as soon as xanth finishes running expire (assuming I'm still awake then...) ...tad