[tor-dev] The Torouter project - where are we now?

Runa A. Sandvik runa.sandvik at gmail.com
Sun Apr 24 08:14:06 UTC 2011


On Sun, Apr 24, 2011 at 3:55 AM, Jacob Appelbaum <jacob at appelbaum.net> wrote:
> On 04/23/2011 04:32 PM, Erinn Clark wrote:
>> * Jacob Appelbaum <jacob at appelbaum.net> [2011:04:21 11:54 -0700]:
>>> It's a question for what we as a project can handle supporting - when a
>>> new Tor is released, we'll need to build it unless we rely on upstream
>>> builds. Runa and I suggest that we (Tor) may want our own OpenWRT
>>> repository - that by default seems to fall directly on our main build
>>> person, I think.
>>
>> Jake and I discussed this on IRC and the basic summary is that for now we'll
>> wait and see -- probably longer term we can support maintaining a repository,
>> if that turns out to be the right route, but my role is going to be mainly
>> infrastructure related so I can help make sure people are able to do what they
>> need without blocking on me.
>
> One other important point made in that discussion is that no one seems
> to have time for supporting an entirely new platform for every Tor
> release. So while The Tor Project may support it - we have no one
> willing to bell the cat today.
>
> What this means practically is that as we've seen with Android, we're
> going to seriously lag releases as it won't be the responsibility of any
> single person or group of people. This won't work if we ship our own OS
> (such as a custom OpenWRT image) and it will simply be difficult if
> we're just shipping Tor (with or without supporting libraries).

We already know that we can't rely on upstream builds. If we want to
our users to have the latest version of Tor, we need to set up an okpg
repository ourselves.

Jake; it was my impression that you wanted to do this. Is that not the
case anymore?

-- 
Runa A. Sandvik


More information about the tor-dev mailing list