[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: GSoC Idea: Packaging Tor+Vidalia

To: or-talk@xxxxxxxxxxxxx
Subject: Re: GSoC Idea: Packaging Tor+Vidalia
From: Jacob Appelbaum <jacob@xxxxxxxxxxxxx>
Date: Mon, 24 Mar 2008 01:37:17 -0700
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 24 Mar 2008 04:37:22 -0400
In-reply-to: <20080322094349.GA3167@xxxxxxxxxxxxxxxxxxx>
References: <200803211516.27342.ldoctors@xxxxxxxxxxxxx> <20080321185356.C6061C83E9@xxxxxxxxxxxxxxxxx> <20080322094349.GA3167@xxxxxxxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Icedove 1.5.0.14pre (X11/20080208)

Peter Palfrader wrote:
> On Fri, 21 Mar 2008, Adna rim wrote:
> 
>> My solution at the moment is stopping the tor daemon and removing it
>> from the runlevels through vidalia's postinst script.
> 
> Mucking with another package's config is a serious policy violation.
> Such a package would never be acceptable for Debian.
> 
> 

That was my thought as well. However, I'm curious what your thoughts are
on the Debian Way (TM) to solve this problem? Perhaps to patch the tor
init.d script in the Tor package to check for a flag that can be set by
the Vadalia package?

Regards,
Jacob

Follow-Ups:
- Re: GSoC Idea: Packaging Tor+Vidalia
  - From: Peter Palfrader

References:
- GSoC Idea: Packaging Tor+Vidalia
  - From: Leandro Doctors
- Re: GSoC Idea: Packaging Tor+Vidalia
  - From: Adna rim
- Re: GSoC Idea: Packaging Tor+Vidalia
  - From: Peter Palfrader

Prev by Author: Re: Tor on the OLPC: Working as a server!
Next by Author: Tor Browser web page
Previous by thread: Re: GSoC Idea: Packaging Tor+Vidalia
Next by thread: Re: GSoC Idea: Packaging Tor+Vidalia
Index(es):
- Author
- Thread