From owner-cvs-usrsbin  Thu Mar  2 18:27:59 1995
Return-Path: cvs-usrsbin-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA25091 for cvs-usrsbin-outgoing; Thu, 2 Mar 1995 18:27:59 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id SAA25077; Thu, 2 Mar 1995 18:27:42 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA13279; Fri, 3 Mar 1995 13:24:15 +1100
Date: Fri, 3 Mar 1995 13:24:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199503030224.NAA13279@godzilla.zeta.org.au>
To: CVS-commiters@freefall.cdrom.com, cvs-usrsbin@freefall.cdrom.com,
        wpaul@freefall.cdrom.com
Subject: Re: cvs commit: src/usr.sbin/bootparamd/bootparamd Makefile
Sender: cvs-usrsbin-owner@freebsd.org
Precedence: bulk

>  Modified:    usr.sbin/bootparamd/bootparamd Makefile
>  Log:
>  Took out .include "../../Makefile.inc" which shouldn't be needed now that I
>  put a proper Makefile.inc in the top level of the bootparam heirarchy.
>  (Someday I'll learn. *sigh*)

Lots of other Makefiles used ../../Makefile.inc.  The first one that I
checked was named.  named/tools/*/Makefile uses triple ascension from
${.CURDIR} in two places and triple ascension from "." in one place.
I'm not sure if this is bogus (apart from the ${.CURDIR}.  If the
intermediate Makefile.inc doesn't do anything special it seems better to
include the top level Makefile.inc explicitly.  Perhaps the path to the
controlling Makefile.inc should be passed on to sub-makes.  bsd.prog.mk
etc. could include this instead of ../Makefile.inc.  An intermediate
Makefile.inc could change the path to make itself the controlling one.

Bruce