From owner-freebsd-current Tue Jul 25 02:47:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id CAA18683 for current-outgoing; Tue, 25 Jul 1995 02:47:17 -0700 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id CAA18677 for ; Tue, 25 Jul 1995 02:47:14 -0700 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id TAA02359; Tue, 25 Jul 1995 19:31:40 +0930 From: Michael Smith Message-Id: <199507251001.TAA02359@genesis.atrad.adelaide.edu.au> Subject: Re: Knobs in /etc/sysconfig To: asami@CS.Berkeley.EDU (Satoshi Asami) Date: Tue, 25 Jul 1995 19:31:39 +0930 (CST) Cc: jkh@time.cdrom.com, rgrimes@gndrsh.aac.dev.com, current@freebsd.org In-Reply-To: <199507250807.BAA03432@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Jul 25, 95 01:07:33 am Content-Type: text Content-Length: 1915 Sender: current-owner@freebsd.org Precedence: bulk Satoshi Asami stands accused of saying: > At various points of the startup, all the scripts with sequence number > will be called from system rc files. They will be sorted in shell > globbing order (so the comes in here, if we have inter- > dependencies among ports). This won't work very well, unfortunately. You'd have to give every port in this category a unique and permanent sequence number, starting with a huge inter-number spacing to allow for insertions, or some variation on this idea. If you can handle keeping a list of 'what goes before/what goes after' for each port, then a sequentially arranged list in a control file could be realistically managed, with entries inserted and deleted as packages come and go. > Then the job of pkg_add is just to add this file, and pkg_delete to > just delete this file. The porter's job is to write this script so > that the program will be started up with reasonable arguments, and > check other ports to see if there are any dependencies. This makes automation easier, but increases (substantially) the pain for work-by-hand. I'm lukewarm, I suspect other will Not Like It Very Much At All 8) > Can't get any simpler than this. :) The current state of the art is pretty simple, just messy. The real question here I guess is whether there is sufficient support for an approach favourable to automated interaction. Are we ready for a 'never edit the files, just use the editing tools' approach a 'la Solaris, or do we want a middle ground solution? > Satoshi -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" - Terry Lambert [[