Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pacbell.com!pacbell!zorch!hico2!kak From: kak@hico2.UUCP (Kris A. Kugel) Newsgroups: comp.sys.3b1 Subject: Re: comp.sources.3b1 Summary: this is a directed graph Message-ID: <1180@hico2.UUCP> Date: 5 Mar 91 21:48:29 GMT References: <326@sialis.mn.org> <11381@pbhya.PacBell.COM> <1991Feb22.032323.10265@ceilidh.beartrack.com> Organization: High Country Software Lines: 27 In article <1991Feb22.032323.10265@ceilidh.beartrack.com>, dnichols@ceilidh.beartrack.com (DoN Nichols) writes: > > - to include clues to the code, items, things other than come with a stock > > 3b1, that posted source depends on. > > Add to that a note in the notes with the sources archives on osu-cis > which suggest other packages which should be snarfed at the same time to > complete a project. > Donald Nichols (DoN.) I dunno, I suspect what we need is a standard map, not one for each project. If I'm no longer sure of all the modifications I've added to my 3b1's hardware and software, I may make a mistake when specifying what you need to run/compile the stuff. Large projects choke on this kind of activity; at least some good stuff gets out the door for the 3b1, and nobody's sinking money to pay for development overhead. If somebody wants to volunteer to spend the 100-hours or more to organize, document, and make dependency graphs for the user and other generated software available on osu-cis and other places, I'll cheer them on. But without an economic incentive, who has time to do it? Kris A. Kugel ( 908 ) 842-2707 uunet!tsdiag.ccur.com!hico2!kak {daver,ditka,zorch}!hico2!kak internet: kak@hico2.westmark.com