From owner-freebsd-small Mon Jul 24 23:16: 6 2000 Delivered-To: freebsd-small@freebsd.org Received: from lepton.subatomix.com (okc-27-143-173.mmcable.com [24.27.143.173]) by hub.freebsd.org (Postfix) with ESMTP id AA40037B75B for ; Mon, 24 Jul 2000 23:16:00 -0700 (PDT) (envelope-from jss@lepton.subatomix.com) Received: from localhost (jss@localhost) by lepton.subatomix.com (8.9.3/8.9.3) with ESMTP id BAA08213; Tue, 25 Jul 2000 01:17:59 -0500 (CDT) (envelope-from jss@lepton.subatomix.com) Date: Tue, 25 Jul 2000 01:17:58 -0500 (CDT) From: "Jeffrey S. Sharp" To: W Gerald Hicks Cc: freebsd-small@FreeBSD.ORG, jhix@jhix.mindspring.com Subject: Re: TinyBSD kit progress report In-Reply-To: <200007250523.WAA05741@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000, W Gerald Hicks wrote: > > > I've been wondering a bit, after someone brought it up a while back: what > > are the chances of the TinyBSD kit making it into the FreeBSD source tree > > once it's good enough? > > It seems to me that it would be a lot more interesting to have the > ports/build frameworks set up to accomodate building "these things" > out of the src/ tree. > ... > ports/itsybsd anyone? :-) Interesting idea, but there are some things about small freebsd kits that are tightly coupled to the underlying system. Imagine the differences introduced when installing the port onto systems from different branches... Sure, we could make it happen with some Makefile/patch magic, but having the kit in src/release seems like the simpler solution IMHO. =============================== Jeffrey S. Sharp jss@subatomix.com -----BEGIN GEEK CODE BLOCK----- Version 3.12 GCS/IT/MU d-@ s-:+ a21 C++(++++) UBL+(+++$)> P L+(+++$)> E+> W++ N+(++) o? K? w++$> !O M(-) !V PS+ PE Y PGP- t+ 5 X+ R(+) tv+ b+ DI++(+++) G++ e> h--- r+++ y+++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message