On Wed, Apr 25, 2012 at 10:43:59AM -0700, Jason Evans wrote:
> On Apr 25, 2012, at 9:39 AM, Ruslan Ermilov wrote:
> > So you removed _malloc_options that was part of the documented
> > programming API, while some software made use of it.
[...]
> > Please explore the possibility to add backwards com
On Wed, Apr 25, 2012 at 09:37:36PM -0700, Tim Kientzle wrote:
> 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.
Well, actually, portmgr@. Send a PR with [exp-run] in the Sy
On Apr 25, 2012, at 10:43 AM, Jason Evans wrote:
>
> 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 appr
On Apr 25, 2012, at 9:39 AM, Ruslan Ermilov wrote:
> So you removed _malloc_options that was part of the documented
> programming API, while some software made use of it.
>
> While removing part of the documented API was definitely a bad
> idea, you didn't provide any mean to detect this change
>
On Tue, Apr 17, 2012 at 12:34:20PM -0700, Jason Evans wrote:
> As a result of the recent jemalloc update, the format for
> /etc/malloc.conf has changed. If your system has an old-style
> /etc/malloc.conf, you will want to delete it prior to
> installworld, and optionally re-create it using the new
As a result of the recent jemalloc update, the format for /etc/malloc.conf has
changed. If your system has an old-style /etc/malloc.conf, you will want to
delete it prior to installworld, and optionally re-create it using the new
format after rebooting. See malloc.conf(5) for details (specific
