Xref: utzoo comp.sources.d:5968 alt.sources.d:1030
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!ogicse!pdxgate!qiclab!techbook!jamesd
From: jamesd@techbook.com (James Deibele)
Newsgroups: comp.sources.d,alt.sources.d
Subject: How do you handle archiving sources?
Message-ID: <1990Nov20.070613.27034@techbook.com>
Date: 20 Nov 90 07:06:13 GMT
Reply-To: jamesd@techbook.com (James Deibele)
Organization: TECHbooks - Beaverton, Oregon - Public Access Unix
Lines: 27

I'd like to make a lot of the sources I've acquired in alt.sources and the
various comp.sources.* groups available in the near future.  However, none
of the ways that I've come up with for presenting the files has particularly
thrilled me.  So ...

How do you handle archiving these groups?  Do you have a magic shell program
that captures the detailed description to a file for closer examination? (I 
would like to see all replacement gettys with an accurate one-line description,
then based on the description, I'd like to be able to examine those detailed
versions for one or two that caught my eye.)

How do you handle patches?  Do you apply them?  Or do you tar them up with
the original distribution file?  Is there somebody who you think does this
type of thing particularly well?

What's particularly annoying for me are these little C programs that I've
picked up --- they have the potential to be a life-saver for someone who
needs that routine, but how do you make up a useful list of these things?

Anyay, the archives might not be available here for a while.  But it seems 
like this should be of general interest.  

Thanks!

--
Public Access UNIX at (503) 644-8135 (1200/2400) Voice: +1 503 646-8257
Authorized ESIX, SCO resellers --- Great products at a GREAT price