[Pkg-anonymity-tools] Please put obfs4proxy in wheezy-backports

[isis]

intrigeri transcribed 0.9K bytes:
> Hi,
> 
> isis wrote (02 Feb 2015 22:09:11 GMT) :
> > I was wondering: would it be possible to put the obfs4proxy package into
> > wheezy-backports [...]
> 
> This requires backporting first at least golang-ed25519-dev,
> golang-goptlib-dev, golang-go.crypto-dev, golang-go.net-dev and
> golang-siphash-dev. And then, in turn, possibly some of their own
> {build,runtime}-dependencies. I suspect that if it was doable without
> lots of work, Lunar would have done it already.

For Go binaries, the default is to build with static linking.  I hear that it
is possible to build dynamically-linked Go binaries using gccgo, however I
have not tried.  So, assuming that obfs4proxy is built with the default Go
tools, not gccgo, these additional dependencies should be build-time
dependencies only.  Is there a Debian policy rule that whatever is required to
build a package must also be available in the distribution channel that the
package is available in?

> If my guess is right, with my Debian contributor hat, I think we'd
> better put efforts into making sure that Jessie is released soon
> enough (~mid March is my current best estimated), than into trying to
> backport that pile of Go libraries for Wheezy.

That makes perfect sense.

> (Now, with my Tails developer hat, given I doubt Tails based on Jessie
> is out before next October, I'd be happy to see backports for
> Wheezy...)

That is starting to sound more complicated. :(

-- 
 ♥Ⓐ isis agora lovecruft
_________________________________________________________
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://blog.patternsinthevoid.net/isis.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1154 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-anonymity-tools/attachments/20150203/9b17a50a/attachment.sig>