[tahoe-dev] [tahoe-lafs] #867: use ipv6

David-Sarah Hopwood david-sarah at jacaranda.org
Sat Feb 16 17:05:08 UTC 2013


On 16/02/13 12:49, Randall Mason wrote:
> On Fri, Feb 15, 2013 at 4:28 PM, <kpneal at pobox.com <mailto:kpneal at pobox.com>> wrote:
> 
>     Is there really a need to restate the protocol next to the address? The
>     two address formats (dotted quad vs colons) are different enough that it
>     should already be clear which is which. Just curious.
> 
> The discussion happened for that here: [Foolscap
> 155](http://foolscap.lothar.com/trac/ticket/155).  It's more about making things easier to
> be backward compatible and future proof than "needing" it for future.  This has nothing to
> do with my changes and foolscap is more a part of Twisted than it is part of Tahoe-LAFS,
> even if Brian Warner is a main figure behind both.  It is stated that foolscap changes
> should be discussed on the Twisted mailing list.  We're using Foolscap to abstract away
> networking from us and because of that we don't need to worry about this type of thing.

While I remember: Because of http://foolscap.lothar.com/trac/ticket/155#comment:6 ,
on your IPv6 branch please change Tahoe's dependency on Twisted (in
src/allmydata/_auto_deps.py) to >= 12.1.0, as changing the dependency on foolscap
to the version that supports IPv6.

(While setuptools/zetuptoolz/distribute would take note of the indirect dependency
on >= 12.1.0 via foolscap anyway, this makes it clearer what version Tahoe code can
rely on.)

-- 
David-Sarah Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130216/d1d08303/attachment.asc>


More information about the tahoe-dev mailing list