On 06/07/2011 10:23, Marco Bonetti wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/05/2011 07:46 PM, Antonio Hernández Blas wrote:
Also in tor´s README.
I'm updating rc.tor right now to get rid of hardcoded parameters, so
I also took the time to tidy up the whole package. Any suggested
wording except for the already present "This package requires
libevent"? I mean, this time we need to rebuild the package as
libevent went under an major change (1.4 -> 2.0) but it shouldn't
be done at every libevent upgrade.
How about "if you have recently upgraded libevent from the 1.4 series to
the 2.0 series, Tor will need to be recompiled against the new 2.0 version".
If I remember correctly, there was
a minor libevent update some times ago (1.4.x -> 1.4.y) and Tor
didn't break down but I can't confirm this as slackbuilds.org looks
down :-P
Works for me :)
http://www.downforeveryoneorjustme.com/www.slackbuilds.org
Ciao, Marco
Pierre
- -- Marco Bonetti Tor research and other stuff:
http://sid77.slackware.it/ Slackintosh Linux Project Developer:
http://workaround.ch/ Linux-live for powerpc:
http://workaround.ch/pub/rsync/mb/linux-live/
My GnuPG key id: 0x0B60BC5F -----BEGIN PGP SIGNATURE----- Version:
GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk4UKaoACgkQTYvJ9gtgvF9vygCgpEhsN4jr1T48qDde62PEWlR9
fecAoKl40SQz7cXQGYnH7HEdkYv6sQna =OZQb -----END PGP SIGNATURE-----
_______________________________________________ SlackBuilds-users
mailing list [email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
