update 0.0.14 considered very important by both Vidalia and TOR Reproducible: Always
*** Bug 205522 has been marked as a duplicate of this bug. ***
*** Bug 212342 has been marked as a duplicate of this bug. ***
on 24-March-2008 Vidalia 0.1.2 was released (change summary please)
Created attachment 147382 [details] Proposed ebuild for vidalia-0.1.2 It works well for me. I skipped the warning present in the latest ebuild in portage about copying torrc to the users' homes as that implies running an instance of Tor for each user. I believe a single system-wide instance of Tor is preferable and what most people use.
Created attachment 147383 [details] net-misc/vidalia-0.1.2.ebuild It works for me (I got the cmake part from the app-cdr/cdrkit ebuild)
(In reply to comment #4) > It works well for me. I skipped the warning present in the latest ebuild in > portage about copying torrc to the users' homes as that implies running an > instance of Tor for each user. I believe a single system-wide instance of Tor > is preferable and what most people use. Your ebuild looks cleaner then mine but I'd suggest to fix the RDEPEND, vidalia doesn't depend on cmake to run. Are you able to use a running tor process with vidalia? Accordingly with http://trac.vidalia-project.net/ticket/339 it should be possible, but when I click "start tor" vidalia doesn't recognize the running tor and try to start another one. I thought it could be a permission issue but I obtain the same behavior running vidalia as root.
Oops, I forgot to say that I think we don't need to install LICENSE* because they are all in /usr/portage/licenses
Created attachment 147385 [details] Proposed ebuild for vidalia-0.1.2 Ops, just noticed a stray line from something I tried earlier that is not necessary any longer.
I found it: http://trac.vidalia-project.net/wiki/FAQ#ExistingTor I think should be useful to add this URL in the pkg_postinst() ;)
Actually there is a tor bug that probably prevents a working system-wide tor + vidalia ran as unprivileged user configuration. I submitted a bugreport upstream http://bugs.noreply.org/flyspray/index.php?do=details&id=643
Funny that we submitted an ebuild almost at the same time. There definitely seems to be issues with the authentication. Unfortunately I do not have time to investigate this now. If you want, feel free to merge the best of my ebuild into your as you see fit.
Added 0.1.7 (latest version) to portage.
