Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site mordred.purdue.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!pucc-j!purdue!sbm
From: sbm@purdue.UUCP (Steve Munson)
Newsgroups: net.micro.mac
Subject: Re: FPack for Macintosh
Message-ID: <450@mordred.purdue.UUCP>
Date: Mon, 20-Jan-86 23:19:05 EST
Article-I.D.: mordred.450
Posted: Mon Jan 20 23:19:05 1986
Date-Received: Wed, 22-Jan-86 05:39:15 EST
References: <8081@amdcad.UUCP> <1113@arthur.purdue.UUCP> <8388@amdcad.UUCP>
Organization: Department of Computer Science, Purdue University
Lines: 36
Keywords: FPack Ascii file packager
Summary: HUH?

In article <8388@amdcad.UUCP>, jimb@amdcad.UUCP (Jim Budler) writes:
> ...Now how do I transport those source to the Mac? I
> unshar them, then I macput -u each one of them????

     Geez, I must be confused.  If you know how to use the shell, you
say

	for file in *
	do
		macput -u $file
	done

right?  The point is that unsharing on UNIX and downloading scores of
files at once to the Macintosh is easy (can be done automatically).
Anything that gets in the way of this process, like packit or any
Macintosh file munger without a UNIX equivalent, is a hindrance.  Once a
large file gets to the Macintosh, it becomes much more difficult to
convert further.

> Now if you want to write a packit compatible Unix program which can unpack
> and pack packit files on Unix, go ahead.

     I wish someone would, or even better yet, stop posting packitted
files; use shar instead (I know, not as much data compression).

> Or if you want to write a /bin/sh
> compatible unpacker for the Mac, go ahead.

     That would be a waste of time, and, as I understand it, that is
what you are doing, right?

     Am I missing something really obvious here?
-- 
					Steve Munson
					sbm@Purdue.EDU
					sbm@Purdue.CSNET