From owner-freebsd-current@FreeBSD.ORG  Tue May 27 21:52:46 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6AFBE37B401
	for <freebsd-current@freebsd.org>;
	Tue, 27 May 2003 21:52:46 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 917A343F3F
	for <freebsd-current@freebsd.org>;
	Tue, 27 May 2003 21:52:45 -0700 (PDT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4S4qOkA059847;
	Tue, 27 May 2003 22:52:24 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Tue, 27 May 2003 22:52:07 -0600 (MDT)
Message-Id: <20030527.225207.101586684.imp@bsdimp.com>
To: doconnor@gsoft.com.au
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <200305281147.53271.doconnor@gsoft.com.au>
References: <C90CF9CA-9040-11D7-941E-0003937E39E0@mac.com>
	<200305281147.53271.doconnor@gsoft.com.au>
X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: policy on GPL'd drivers?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 May 2003 04:52:46 -0000

In message: <200305281147.53271.doconnor@gsoft.com.au>
            "Daniel O'Connor" <doconnor@gsoft.com.au> writes:
: The only downside is that there are no hooks into the build process so you 
: have to be VERY careful when you update your kernel, or you get panics :(

This is true.  I'd thought that MODULES_OVERRIDE would help, but ports
builds and kernel builds are different enough to make this not easy to
do.

Wanna test a patch?  Add a 'makeoptions PORTS_MODULES=comms/ltmdm' to
your config file and apply the following patch.  Lemme know how well
(or poorly) it works.  There's likely some hidden assumptions that
make it appear to work for me.

Warner

--- sys/conf/kern.post.mk#10	Tue May 27 22:34:04 2003
+++ sys/conf/kern.post.mk	Tue May 27 22:34:04 2003
@@ -41,6 +41,20 @@
 .endif
 .endif
 
+.if defined(PORTS_MODULES)
+modules: ports-all
+ports-all:
+.for __i in ${PORTS_MODULES}
+	cd /usr/ports/${__i}; ${MAKE} all
+.endfor
+
+modules-install: ports-install
+ports-install:
+.for __i in ${PORTS_MODULES}
+	cd /usr/ports/${__i}; ${MAKE} install
+.endfor
+.endif
+
 .if !defined(DEBUG)
 FULLKERNEL=	${KERNEL_KO}
 .else