home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!sample.eng.ohio-state.edu!purdue!mentor.cc.purdue.edu!news
- From: ab@nova.cc.purdue.edu (Allen B)
- Newsgroups: comp.sys.next.misc
- Subject: Re: Stripping apps (was Re: Missile Command and Other Submissions)
- Message-ID: <BtLLGL.t9@mentor.cc.purdue.edu>
- Date: 26 Aug 92 15:53:08 GMT
- References: <1992Aug25.030555.6954@jhunix.hcf.jhu.edu>
- Sender: news@mentor.cc.purdue.edu (USENET News)
- Organization: Purdue University
- Lines: 34
-
- In article <1992Aug25.030555.6954@jhunix.hcf.jhu.edu>
- incubus@jhunix.hcf.jhu.edu (Alexander Swietlicki) writes:
- >
- > For all those interested, here is a list of some app sizes before
- > and after stripping.
-
- As others have said, you can't strip all these
- applications. I encourage submitters to strip binaries
- (look at README in the submissions directory for other
- suggestions) or to document that the file should not be
- stripped. I made the mistake of stripping MediaView and
- learned that lesson quickly. :-)
-
- I recompile all submitted sources and check them against
- the submitted binary. If it's not stripped and not
- documented otherwise, I usually contact the
- author/submitter for more information.
-
- Binaries get a little less attention. Demos get nearly
- none (as you're expected to contact the vendor anyway)
- unless there's a big problem. That's why demos usually
- get filed rather quickly.
-
- If you've found a binary on sonata/nova that you think
- ought to be stripped, try contacting the author or
- submitter first. If that doesn't work, hit
- archive-management@cc.purdue.edu.
-
- Also remember that unstripped binaries often compress
- to nearly the same size as their stripped counterparts,
- so it might not be as bad as you think (for us- installation
- is different, of course).
-
- Allen B (Keepin' busy)
-