From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 28 Mar 2010 16:04:51 -0400
To: 9fans@9fans.net
Message-ID: <dbb1f6350f1dd900dc8340364d133d04@ladd.quanstro.net>
In-Reply-To: <32d987d51003281236m7a890b0dkaf4de23191fa3d47@mail.gmail.com>
References: <20100325114948.GA7249@polynum.com>
	<twig.1269564722.70572@swcp.com> <twig.1269579741.2777@swcp.com>
	<31C84C15-2EE3-46CA-BE9F-48F20886ADF7@fastmail.fm>
	<Pine.BSI.4.64.1003270644190.23363@malasada.lava.net>
	<202b36ec0f14adf4b09e53052147ccc8@brasstown.quanstro.net>
	<11721B64-8041-4D96-94E3-49472F941C38@fastmail.fm>
	<32d987d51003281236m7a890b0dkaf4de23191fa3d47@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Man pages for add-ons
Topicbox-Message-UUID: f70b7e3c-ead5-11e9-9d60-3106f5b1d025

> another concern I have is where are you going to put 3rd party drivers
> a new location is going to be created, probably a directory per 3rd
> party driver, when all this ends?

i don't think this is on point, but since your brought it
up, i run into a related problem all the time.  how to
organize stuff that clearly doesn't belong in the distribution,
like experimental network stacks, etc.  (i keep all the
normal stuff like network drivers in the usual places.)

what i settled on was a tiny little script ../port/dirdep
which allows one to specify a "dir" section in the kernel
config.  one line of support was added in ../pc/mkfile.
the script includes ../$dir/mkfrag if it exists so that all
the add-hoc rules one needs can be included.
this way you can build a kernel with, say, an
xns stack, without major upheaval in ../pc/mkfile and
you can build devices and whatnot directly from the
included directory.

- erik