Date: Wed, 25 Apr 2012 21:37:36 -0700 From: Tim Kientzle <tim@kientzle.com> To: Jason Evans <jasone@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: /etc/malloc.conf format change Message-ID: <AA0B5374-DD7E-4452-AB0C-E09D89D1DEED@kientzle.com> In-Reply-To: <0D8D93F3-5919-4A48-9BB2-887E4420C162@freebsd.org> References: <7FC153A1-8815-4BAE-AB94-FED51DBFFEAA@freebsd.org> <20120425163949.GA53937@lo0.su> <0D8D93F3-5919-4A48-9BB2-887E4420C162@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 25, 2012, at 10:43 AM, Jason Evans wrote: >=20 > On a related note, is there any way to find all ports that refer to = _malloc_options without extracting source for all of them? I considered = being proactive about finding software that depends on _malloc_options, = but no tractable approaches came to mind. Yes, there actually is. The Ports maintainers will run "experimental" ports builds on the port build clusters to help verify potentially disruptive changes like this before they are committed. Ask on ports@ for more details. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AA0B5374-DD7E-4452-AB0C-E09D89D1DEED>