From owner-freebsd-current Wed Jul 30 22:54:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA06128 for current-outgoing; Wed, 30 Jul 1997 22:54:38 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA06121 for ; Wed, 30 Jul 1997 22:54:34 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id WAA14109; Wed, 30 Jul 1997 22:54:25 -0700 (PDT) Date: Wed, 30 Jul 1997 22:54:25 -0700 (PDT) Message-Id: <199707310554.WAA14109@silvia.HIP.Berkeley.EDU> To: chuckr@glue.umd.edu CC: freebsd-current@freefall.FreeBSD.org In-reply-to: (message from Chuck Robey on Wed, 30 Jul 1997 18:49:25 -0400 (EDT)) Subject: Re: core group topics From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I was wondering if core has been discussing the two topics lately that * can't really move without core approval? Sorry, I've been busy/away for the past few days. * 1) Satoshi's new Makefile. His makefile has been around plenty long This is not a "policy" issue anyway, I don't think core's approval is needed. (Right, the rest of core? :) * enough for testing, and while several people have reported good results, * I've seen no negatives reported at all. Will it get ignored or committed? It will be committed soon. I had the impression that Bruce was unhappy about some of the environment variables, but haven't gotten around to verify what exactly is the fix. However, I don't have a -current machine to test anymore, so I'm not sure if I can support -current. I'll send out a patch for -stable later tonight. * 2) John Polstra's ELF work. He's done all the work that anyone could * possibly want, to move FreeBSD to ELF. There are several good reasons to * move, and none excepting inertia not to. I know that moving FreeBSD to * ELF isn't a high priority project, but all the work's been done, the * benefits are real, and it's high time to consider it. This would have to be decided by core. Myself, I have no idea what ELF offers that a.out doesn't (other than what John said), but if we can get rid of the "text relocation error" that pops up all over the place during package builds, that's good news enough for me. :) Satoshi