current vidalia ebuild depends on net-misc/tor (RDEPEND), accordling with vidalia documentation, is possible to use vidalia with an external tor process (already running on a different host) using tor directives "ControlPort" and "HashedControlPassword". So it's useless to install by default tor with vidalia on the same host when you are going to control an external tor process, this dependency should be controlled/disabled via a local USE flag (eg: externaltor,notor). Reproducible: Always Steps to Reproduce: 1.emerge net-misc/vidalia to control an external tor process 2. 3. Actual Results: net-misc/tor is installed by default Expected Results: net-misc/tor dependency should be controlled/disabled via USE flag
Upstream is a bit confusing, they have enabled the use of a remote tor host, and it builds without tor, but documentation says it needs tor >= 0.2.0.34 . Have you tested if vidalia works _fine_ without tor installed ?
(In reply to comment #1) > Upstream is a bit confusing, they have enabled the use of a remote tor host, > and it builds without tor, but documentation says it needs tor >= 0.2.0.34 . > > Have you tested if vidalia works _fine_ without tor installed ? > hi, just tested net-misc/vidalia-0.2.6 (locally bumped, i removed tor from RDEPEND) with a remote net-misc/tor-0.2.0.35 istance. I was able to connect/control the remote istance of tor, after setting properly ControlListenAddress and HashedControlPassword settings on it.
Applied to net-misc/vidalia-0.2.6 , thanks for the report