From owner-freebsd-arch@FreeBSD.ORG Wed Jun 27 18:46:36 2007 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0712316A41F for ; Wed, 27 Jun 2007 18:46:36 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9E17D13C43E for ; Wed, 27 Jun 2007 18:46:35 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id l5RIUnb0052769 for ; Wed, 27 Jun 2007 13:30:49 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Wed, 27 Jun 2007 13:29:23 -0500 (CDT) From: "Sean C. Farley" To: freebsd-arch@FreeBSD.org Message-ID: <20070627130518.M12708@thor.farley.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on mail.farley.org Cc: Subject: setenv() update in 7-CURRENT time frame X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 18:46:36 -0000 With the release rapidly approaching, I want to know if it would be better to move the setenv() (and family) API to POSIX (along with added memory leak restraints). For details on the changes, please see my posting in the current@ and ports@[1] archives. I ask arch@ since it involves API changes. I thought about holding off until the branching, but enough changes have rolled into CURRENT to make me think that it may be acceptable. I received no complaints from my postings in current@ and ports@. From communications with Kris Kennaway, he surmised it may affect a few old BSD-specific ports and checking would have to be done manually to find them. How does the idea of applying my patch[1] to CURRENT before the branch is made sound? While I would prefer it to make it into this release, I understand if it would be best to wait. I am just looking for a definitive answer. If I did not ask, I would feel anxious wondering if it could have made it. :) Sean 1. http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/041577.html 2. http://www.farley.org/freebsd/tmp/setenv/setenv.diff -- scf@FreeBSD.org