From owner-freebsd-current  Thu Nov  9 15:19:57 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA11314
          for current-outgoing; Thu, 9 Nov 1995 15:19:57 -0800
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA11259
          ; Thu, 9 Nov 1995 15:19:39 -0800
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA02126; Thu, 9 Nov 1995 16:15:10 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199511092315.QAA02126@phaeton.artisoft.com>
Subject: Re: config, other kernel build tools
To: gibbs@freefall.freebsd.org (Justin T. Gibbs)
Date: Thu, 9 Nov 1995 16:15:09 -0700 (MST)
Cc: terry@lambert.org, gibbs@freefall.freebsd.org, current@FreeBSD.org,
        hackers@FreeBSD.org
In-Reply-To: <199511092122.NAA06512@aslan.cdrom.com> from "Justin T. Gibbs" at Nov 9, 95 01:22:04 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1451      
Sender: owner-current@FreeBSD.org
Precedence: bulk

> >I *don't* want to toast my existing /usr/sbin/config; I like it, it
> >is my friend, it serves me well.
> 
> Than change DESTDIR in your alternate source tree before you do the install. :)

and chroot to use it, etc., setc..  8-(.

> >What I'd really like is an incremental step in Richard's planned
> >mega-makefile patch direction.  Putting the tools that are only good
> >for building kernels in with the kernel code that is to be built is
> >a good first step.
> 
> So you advocate is gets installed into the conf dir?  Ugh.

Yeah, just like the X tools during an X build.  Not pretty, but
non-colliding with existing installations.

> >It's not like the boot code, etc. isn't already in the kernel tree
> >and isn't really kernel code proper.
> 
> The main reason we want to do away with config is that it just isn't
> flexible enough and we have to hack it all of the time.  If config
> wasn't such a poor utility, there would be nothing wrong with having
> it in /usr/sbin since it would only change once in a blue moon.

Agreed.  The ultimate goal is to kill config entirely.  The short
term goal is to build a -current kernel on a -stable system.

If it's killed, it goes away entirely.  If it's not killed yet, /usr/sbin
is probably the wrong place for it to live until such time as it *is*
killed.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.