Date: Wed, 27 Jun 2007 15:43:58 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-arch@freebsd.org Cc: "Sean C. Farley" <scf@freebsd.org> Subject: Re: setenv() update in 7-CURRENT time frame Message-ID: <200706271543.59223.jhb@freebsd.org> In-Reply-To: <20070627130518.M12708@thor.farley.org> References: <20070627130518.M12708@thor.farley.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 27 June 2007 02:29:23 pm Sean C. Farley wrote: > 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 Go for it. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706271543.59223.jhb>