On Sun, Sep 23, 2012 at 03:35:49PM -0500, Chris Muller wrote:
> Is the image ready for a default value for enableIpv6 of true?
> 

Yes. That's how it has been working for quite some time now. If we default
it to false in trunk, it will just turn into dead code.

I am suggesting that we disable it in the release image so as not to inflict
pain on users of an official release image, but keep it enabled in trunk so
that we either fix it or take a decision to abandon it in favor of something
better.

Dave


> 
> 
> On Sun, Sep 23, 2012 at 12:44 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> > There are problems with the new network support when running on Windows
> > with a newer VM that provides IPv6 primitives. This preference allows the
> > new network support to be disabled.
> >
> > Default setting is true, which enables the new network support (as
> > is currently the case for a trunk image). It can be set false to disable
> > new network support, and I think that this should be done for the
> > Squeak 4.4 release image, otherwise we are going to cause problems
> > for lots of Windows users.
> >
> > If no objections I will move this to trunk in a day or so.
> >
> > Dave
> >
> >
> > On Sun, Sep 23, 2012 at 05:32:54PM +0000, commits at source.squeak.org wrote:
> >> A new version of Network was added to project The Inbox:
> >> http://source.squeak.org/inbox/Network-dtl.137.mcz
> >>
> >> ==================== Summary ====================
> >>
> >> Name: Network-dtl.137
> >> Author: dtl
> >> Time: 23 September 2012, 1:32:32.394 pm
> >> UUID: b4bcd6e4-6a2d-4fc6-be4b-0d01accc3c72
> >> Ancestors: Network-ul.136
> >>
> >> Add a preference for "Enable IPv6 and new network support" in preference category "general". If enabled, IPv6 and the new network support will be enabled if the required primitives are present in the VM, otherwise the new network support is disabled regardless of whether the VM provides IPv6 primitives.
> >>
> >