obfsproxy install instructions page should mention releases

A Debian package of obfsproxy is available from deb.tpo (at least for squeeze and wheezy), and a FreeBSD port is also available. [https://www.torproject.org/projects/obfsproxy-instructions.html.en] should mention them.

A Gentoo port may also be available; CCing the person who would maintain it if it exists.

added component::webpages/website owner::asn priority::medium resolution::wontfix status::closed type::defect labels

The page should also tell users how to use the tarball if they need to build from source, now that there is a tarball.

Trac:
Summary: obfsproxy install instructions page should mention packages, ports to obfsproxy install instructions page should mention releases

For FreeBSD please add the following:

Port: http://www.freshports.org/security/obfsproxy Installation instructions: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html

Trac:
Username: cs

Trac:
Status: new to assigned
Owner: phobos to asn

Trac:
bug5582.patch

adds packages to the obfsproxy-instructions page

Attached a potential patch.

Trac:
Status: assigned to needs_review

Looks good. Please change the following sentence as FreeBSD is NOT Linux.

FROM:

For a fast and easy installation, obfsproxy is available as a package in various GNU/Linux distributions:

TO:

For a fast and easy installation, obfsproxy is available as a package in various GNU/Linux and BSD distributions:

Trac:
Username: cs

Trac:
bug5582_take2.patch

Replying to cs:

Looks good. Please change the following sentence as FreeBSD is NOT Linux.

FROM:

For a fast and easy installation, obfsproxy is available as a package in various GNU/Linux distributions:

TO:

For a fast and easy installation, obfsproxy is available as a package in various GNU/Linux and BSD distributions:

hah oops! attached another patch.

no more complaints :-) Thank you very much.

Trac:
Username: cs

Trac:
bug5582_release_tarball.patch

I also attached a patch that adds instructions for building the release tarballs.

We might be able to make it easier for users to follow these instructions, by always symlinking the latest obfsproxy release to obfsproxy_current.tar.gz in /dist/obfsproxy and linking to that.

Do you really want to keep instructions for git? Developers will figure that out on their own (a link should be sufficient) while other users only need to know how to compile the official tarball.

Second, I would write "get into the source directory" or "switch to the source directory".

Trac:
Username: cs

I'm closing this now as I don't think the patches reflect reality anymore.

Trac:
Resolution: N/A to wontfix
Status: needs_review to closed

closed

moved to tpo/web/trac#5582 (closed)