🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.mac.apps
Article #6699

Re: Compactor - A reason not to use

#6699
From: Matt Rollefson
Date: Fri, 11 Jan 1991 23:56
38 lines
2679 bytes
johnston@oscar.ccm.udel.edu writes:

>In article <YEE.91Jan11113640@pmin7.osf.org>, yee@osf.org (Michael K. Yee) writes...
>>In article <41386@nigel.ee.udel.edu> johnston@oscar.ccm.udel.edu writes:
>>	You've missed my meaning.  FileList 1.4 recognizes enough of the
>>	stuffit and compactor data format to get the list of files in the
>>	archive.  This is a neat feature, because you can keep your files in
>>	compressed format and still get a listing of the FILES stored on
>>	your disks.  I haven't tried FileList 1.4 yet so I may be totally
>>	off base.  :-)
>> 
>Thanks also to Mr. Junio Hamano for making the same point with regard to
>to FileList 1.4.  A Compactor .cpt archive is all data fork ... so anything
>that reads it, reads the "data format", strictly speaking.  Nevertheless,
>it is likely that file/folder information is stored in the file's header
>along with the name, type and creator.  I expect that the people who wrote
>CatStuff and Filelist were able to deduce the header format in a straight-
>forward way; it only makes sense that the author of Compactor would
>incorporate this information in a straight-forward way.

I'm sorry, you're wrong here, at least for CatStuff. It states quite
clearly in the stack that the author of CatStuff asked for, and
received, information about the format of Compactor archives directly
from the author of Compactor, Bill Goodman. It further says that Bill
Goodman was quite helpful and willing to pass on this information. I
don't know if it is personal prejudice or some other reason that caused
you to assume the worst as regards how the authors of these programs
received the necessary information, but I suggest you find out the facts
before posting 'I assume' messages.

Note: This is not, strictly speaking, a flame. I would do it via e-mail,
except that I believe the information in my posting (ie the corrections
as to how the author of CatStuff obtained the information about
Compactor's format) should be available to the net.

>-- Bill (johnston@oscar.ccm.udel.edu)
--
Draphsor vo'drun-Aelf                  draphsor@portia.stanford.edu
Technical Details
Message-ID: <draphsor.663638212@elaine5.stanford.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!agate!shelby!portia.stanford.edu!elaine5.stanford.edu!draphsor
References: <41470@nigel.ee.udel.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!agate!shelby!portia.stanford.edu!elaine5.stanford.edu!draphsor
From: draphsor@elaine5.stanford.edu (Matt Rollefson)
Newsgroups: comp.sys.mac.apps
Subject: Re: Compactor - A reason not to use
Message-ID: <draphsor.663638212@elaine5.stanford.edu>
Date: 11 Jan 91 23:56:52 GMT
References: <41470@nigel.ee.udel.edu>
Sender: news@portia.Stanford.EDU
Distribution: comp
Organization: AIR, Stanford University
Lines: 38