Date: Tue, 13 Jan 2004 09:40:16 -0800 (PST) From: Nate Lawson <nate@root.org> To: Takahashi Yoshihiro <nyan@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/modules/acpi Makefile.inc Message-ID: <20040113093817.E62202@root.org> In-Reply-To: <20040113130843.4702F16A54D@hub.freebsd.org> References: <20040113130843.4702F16A54D@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Jan 2004, Takahashi Yoshihiro wrote: > Added files: > sys/modules/acpi Makefile.inc > Log: > Include "../Makefile.inc" to propagate the configuration to subdirectories. > > Revision Changes Path > 1.1 +3 -0 src/sys/modules/acpi/Makefile.inc (new) > > --- /dev/null Tue Jan 13 05:08:42 2004 > +++ src/sys/modules/acpi/Makefile.inc Tue Jan 13 05:08:27 2004 > @@ -0,0 +1,3 @@ > +# $FreeBSD: /repoman/r/ncvs/src/sys/modules/acpi/Makefile.inc,v 1.1 2004/01/13 13:08:27 nyan Exp $ > + > +.include "../Makefile.inc" Is this the right approach? If you want a single Makefile.inc in /sys/modules, then why not just include ../../Makefile.inc? Why make an empty one that just includes its parent, which leads us to a twisty chain of Makefile.inc's, all the same? -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040113093817.E62202>