jkg@gatech.edu (Jim Greenlee) (01/27/89)
In article <4368@okstate.UUCP> klarich@okstate.UUCP (terry klarich) writes: >Does anyone know where I can get the newest version of mskermit? I had it >once, but can't find it. I don't have ftp or uucp. So, I need a bbs >number or Unix login. I can down load with zmodem and kermit. I have the complete Kermit 2.32 distribution (executables for IBM and MS, docs, etc.) that I am willing to submit to comp.binaries if there is sufficient interest. However, I would like to get suggestions from people about what is the most appropriate way of packaging the thing. There was some wailing and gnashing of teeth after I posted version 2.31 last fall, so I'd like to make an effort this time around to do something that works well for a majority of users. Here's a manifest so that everybody can see what I've got (and, more importantly, how big it is): Name Length Stowage SF Size now Date Time CRC ============== ======== ======== ==== ======== ========= ====== ==== mskerm.bwr 14222 Crunched 43% 8112 6 Jan 89 3:38p 4dee mskerm.doc 332577 Crunched 50% 169182 6 Jan 89 3:38p 7ff8 mskerm.hlp 16190 Crunched 46% 8879 6 Jan 89 3:38p 4f94 msr232.upd 20966 Crunched 47% 11166 6 Jan 89 3:39p 0ac7 msvgen.exe 70531 Squeezed 28% 51153 6 Jan 89 3:40p 35da msvibm.exe 101923 Squeezed 25% 77374 6 Jan 89 3:38p 2819 scanchek.c 18428 Crunched 55% 8466 17 Jul 88 10:45a a87b scanchek.exe 9784 Squeezed 10% 8815 17 Jul 88 10:49a 6cde scanchek.hlp 2318 Crunched 35% 1507 17 Jul 88 10:45a 2d6c ====== ======== ==== ======== Total 9 586939 42% 344654 I see three different possibilities for accomplishing this: 1. Post the entire archive as a single unit (uuencoded, of course). I don't favor this option because it would require about a 10 part posting and result in the inevitable flood of "I missed part N" postings (and mail). This was how I got in trouble last time, and I learned my lesson. 2. Post the uuencoded binaries and plain-text documents separately. This should keep the you-should-never-post-archived-text folks happy, but will significantly increase the number of postings required to get the whole thing out (just look at the size of that doc file, folks). It will also probably increase the number of "I missed part N" postings. 3. Post the uuencoded Kermit executables (msvgen.exe and msvibm.exe), the archived and unencoded Scanchek package, and the archived and uuencoded doc files as four separate postings. I favor this idea. The total number of postings will not be significantly different from option (1), and the folks who only need or want a small portion don't have to worry about trying to get the whole thing. I should probably mention that I intend on creating the archives using arc on a UNIX machine. Anybody that has heartburn over that should let me know. In any event, I'll go with the consensus opinion on this. In the event of a tie, I'll ask Ron Heiby to cast the deciding vote (this is a private joke between me and Ron - I just hope Ron gets it :-). Let me know what you think. Jim Greenlee -- Jim Greenlee - Instructor, School of ICS, Georgia Tech jkg@gatech.edu Cato said, "I had rather men should ask why my statue is not set up, than why it is." - Plutarch
bobmon@iuvax.cs.indiana.edu (RAMontante) (01/27/89)
<17841@gatech.edu> jkg@gatech.UUCP (Jim Greenlee) writes: > >I have the complete Kermit 2.32 distribution (executables for IBM and >MS, docs, etc.) that I am willing to submit to comp.binaries if there is >sufficient interest. However, I would like to get suggestions from people >about what is the most appropriate way of packaging the thing. There was My suggestion(s): Send to Rahul Dhesi and let him put them on c.b.i.p -- he's back in business now, so let him slice'n'dice the final packaging. (Do something between your options 2 and 3, via Rahul): Split it into the executables, and the ASCII text. The executables need to be packaged and ascii-ized anyway; the documentation etc. could be distributed as ASCII to make the mailers more efficient. The doc. file is the biggest piece anyway. I think I recall that PAK/ARC etc. have a store-without-compression option, which would do the trick. Certainly ZOO does; and I'd rather see things distributed in ZOO format anyway.