ftp.nice.ch/peanuts/GeneralData/Usenet/news/1989/CSN-89.tar.gz#/comp-sys-next/1989/Nov/where-to-post-bin-src

This is where-to-post-bin-src in view mode; [Up]


Date: Sun 03-Nov-1989 16:58:00 From: Unknown Subject: where to post bin/src This is posting for my friend: he wrote a few utility programs (such as a disassembler) and he wants to distribute it to other NeXT users/programmers. Where is the best place to post these files? Here, or comp.sources.unix? or whatever? Anycase, I am including his read.me file below ------ The HACKKIT Written by Bill Spitzak (SPITZAK@MCIMAIL.COM), Summer 1989. Main features: DIS : a powerful symbolic disassembler, specially designed for looking at mysterious library objects (although it can also disassemble executables). ICONCLOCK : App that draws a clock in it's own icon, yet can be resized to make larger clocks. The clock appearance is in a postscript file and may be edited to customize it. SOURCE CODE: Lots of short, self-contained, source files that demonstrate how to interface with the PostScript server, the Workspace, and the Pasteboard, without using the AppKit routines or "objective C". OTHER FUN THINGS. The file "hackkit.Z" is a compressed tar dump of a directory called "hackkit". To recreate this directory, put "hackkit.Z" in your home directory and type: uncompress -c hackkit | tar xf - You may then delete hackkit.Z. This file was produced by typing "tar cf - hackkit | compress > hackkit.Z" THIS SOFTWARE IS FREE. IT MAY NOT BE SOLD. IT MAY BE FREELY REDISTRIBUTED AS LONG AS ALL SUPPLIED SOURCE CODE IS INCLUDED AND AS LONG AS THIS FILE AND THIS MESSAGE ARE NOT DISTURBED. ----- Richard Man ...!uunet!inmet!rich >From: gerrit@nova.cc.purdue.edu (Gerrit)
Date: Sun 04-Nov-1989 09:56:09 From: Unknown Subject: Re: where to post bin/src In article <32900002@inmet> rich@inmet.inmet.com writes: > >This is posting for my friend: >he wrote a few utility programs (such as a disassembler) and he wants to >distribute it to other NeXT users/programmers. Where is the best place to >post these files? Here, or comp.sources.unix? or whatever? Right now the best place (over the long term, at least) is to send it/them to next-archive@cc.purdue.edu (NeXT attachments are fine, tar/compress/ uuencode works, I can probably deal with uuencoded arc/zoo files if that makes you happy, shar-archives are great, etc.). I will add them to the official NeXT archives which are currently available for ftp. Cs.orst.edu and possibly umd5.umd.edu will pick them up. We are working on getting an email archive server running either on uunet.uu.net or on cc.purdue.edu (or someone else - volunteers let me know!) which will give more general access to those not on the Internet directly. For the short term, it probably wouldn't be terrible to post it uuencoded and such, although I would probably recommend sending it to the above address instead. If I get enough requests for a product, I'll probably post the version from the archives; otherwise I've been e-mailing on demand. Gerrit Huizenga NeXT Workstation Support Purdue University Computing Center gerrit@cc.purdue.edu next-archive@cc.purdue.edu (Anything for or about the archives) >From: jpd00964@uxa.cso.uiuc.edu

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.