From owner-freebsd-stable Fri Mar 13 10:22:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13886 for freebsd-stable-outgoing; Fri, 13 Mar 1998 10:22:34 -0800 (PST) (envelope-from owner-freebsd-stable@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 KAA13818 for ; Fri, 13 Mar 1998 10:22:14 -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 KAA00526; Fri, 13 Mar 1998 10:20:53 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Tom cc: stable@FreeBSD.ORG Subject: Re: include libc_r in 2.2.6 In-reply-to: Your message of "Fri, 13 Mar 1998 10:04:28 PST." Date: Fri, 13 Mar 1998 10:20:53 -0800 Message-ID: <522.889813253@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > It is not like I'm asking for new code to added, just for code that is > already in 2.2.5-stable to be built! The code is there NOW. You just > need to add "WANT_LIBC_R=true" to make.conf Sigh. But that's not the point - I don't do anything to perturb the components of my *build set* after a code freeze. I don't care whether it's part of the system or not, the time to talk about enabling or adding any new component is *well before* a release, not during it or its BETA test cycle. You missed the window. > In case you haven't noticed, this is the second time I've asked this. Yes, the first time you asked was on Friday the 6th of March at 15:49 PST. Code freeze was less than 72 hours away and I was already juggling a number of last-minute items people had thrown at me even earlier in the week. By the time I had a chance to even look at and consider the implications of the issue, code freeze was already upon us and so the idea was tossed on the "think about this after 2.2.6" pile and that's where it's going to stay until after 2.2.6 is tagged and rolled. I simply won't make a change of this type during BETA test, sorry. I'm sure it's totally innocuous and would be of absolutely no harm to anyyone if I added it and to that I can only say that every *other* change I've made which subsequently bit me on the ass in some unforseen fashion has come with exactly the same recommendation and pedigree. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message