Path: utzoo!attcan!uunet!lll-winken!uwm.edu!wuarchive!udel!new
From: new@udel.edu (Darren New)
Newsgroups: comp.sys.amiga
Subject: Re: Self Extracting Archives
Message-ID: <13763@nigel.udel.EDU>
Date: 13 Mar 90 15:45:24 GMT
References: <55.25f441b5@uoft02.utoledo.edu> <195@sai.UUCP> <2675@leah.Albany.Edu> <79.25f87ef0@uoft02.utoledo.edu> <10102@cbmvax.commodore.com> <90.25fc5fd6@uoft02.utoledo.edu>
Sender: usenet@udel.EDU
Reply-To: new@udel.edu (Darren New)
Distribution: na
Organization: University of Delaware
Lines: 15

>> A self unpacking achiver removes this option.  
>   Have you considered this: given a self extracting archive, you can generally
>list the files it contains.  
>[...] This, you can easily check to see what you're executing is really
>an archive.

Actually, the best solution for all would be to have a self-extracting
format that could also be recognised by the standard archive program.
Something like a paramter to zoo or lharc that would say "Tack a
self-extracting header for computer XXX to the front of this archive."
and which could be recognised.  If you already have the archive program
(i.e., zoo or lharc) then just extract normally.,  If you are less
paranoid and you don't have the extracter handy, just execute the
archive.  If you don't HAVE to execute the archive to extract it then
you have the best of both worlds (Hmmm.... cli AND workbench?) -- Darren