Date: Wed, 12 Dec 2001 11:30:04 -0800 (PST) From: Sheldon Hearn <sheldonh@starjuice.net> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/32760: Please MFC /usr/include/malloc.h to -STABLE. Message-ID: <200112121930.fBCJU4R56948@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/32760; it has been noted by GNATS. From: Sheldon Hearn <sheldonh@starjuice.net> To: Alan E <alane@geeksrus.net> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/32760: Please MFC /usr/include/malloc.h to -STABLE. Date: Wed, 12 Dec 2001 21:29:37 +0200 On Wed, 12 Dec 2001 14:10:48 EST, Alan E wrote: > /usr/include/malloc.h on CURRENT generates an error using #error. > /usr/include/malloc.h on STABLE only generates a #warning. > > This means that things (like KDE) will build in STABLE and then people try > to build the released ports on CURRENT and get bit by this. > > If malloc.h were MFC'd, then we'd catch all of this stuff up front, rather > than after releasing new ports to the world. The problem with merging the change onto the stable branch is that it's a serious change of interface in the middle of the lifetime of a major release (4.x). Sure, POSIX-conformant software should look for the prototype in the right place, but we try quite hard to keep point release upgrades as painless as possible. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112121930.fBCJU4R56948>