From owner-freebsd-current  Sat Mar 14 03:34:25 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA22892
          for freebsd-current-outgoing; Sat, 14 Mar 1998 03:34:25 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22886
          for <current@freebsd.org>; Sat, 14 Mar 1998 03:34:17 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA08213;
	Sat, 14 Mar 1998 03:33:02 -0800 (PST)
	(envelope-from jkh@time.cdrom.com)
To: John Birrell <jb@cimlogic.com.au>
cc: current@FreeBSD.ORG
Subject: Re: binutils bloat 
In-reply-to: Your message of "Sat, 14 Mar 1998 21:50:12 +1100."
             <199803141050.VAA18125@cimlogic.com.au> 
Date: Sat, 14 Mar 1998 03:33:02 -0800
Message-ID: <8209.889875182@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I like the idea of being able to pick up a CD with all the supported
> tools installed. So if we do this, are you prepared to build all
> for releases, even though they might not be enabled by default?

I'm not quite sure what you mean by "all" in this context, but I'm
certainly willing to talk about 3.0's release bit generation and
how things might (within reason) be added to it.

					Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message