From owner-freebsd-hackers  Tue Sep 26 00:44:57 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA22511
          for hackers-outgoing; Tue, 26 Sep 1995 00:44:57 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA22506
          for <hackers@freebsd.org>; Tue, 26 Sep 1995 00:44:54 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id AAA16225; Tue, 26 Sep 1995 00:44:43 -0700
Date: Tue, 26 Sep 1995 00:44:43 -0700
Message-Id: <199509260744.AAA16225@silvia.HIP.Berkeley.EDU>
To: jdl@chromatic.com
CC: hackers@freebsd.org
In-reply-to: <199509260541.AAA04042@chrome.jdl.com> (message from Jon Loeliger on Tue, 26 Sep 1995 00:41:18 -0500)
Subject: Re: ports startup scripts
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-hackers@freebsd.org
Precedence: bulk

I thought I was completely lost in this discussion, until this article
hit me like a lightning bolt....

 * From: Jon Loeliger <jdl@chrome.onramp.net>

 * Well, I think these issues point to the more generalized problem
 * of simply representing the "dependency graph".  All of the file number
 * schemes and the single control file schemes are implementations of
 * the general concepts of linearizing a dependency graph.

Yes, *dependency graphs*!  This was what we were all arguing about!
And the Unix way of handling dependency graphs are...yes, "make"!
Can it get any simpler than an /etc/rc.d/Makefile?!? :)

Ok, so who's going to write bsd.rc.mk?  (Me? :)

Satoshi