The current (versioned) patch is: http://nginx.org/patches/spdy/patch.spdy-36.txt If added, it should be controlled via a ‘spdy’ USE flag. It is a patch, not an nginx module, so the modules code in nginx-1.3.1.ebuild, unfortunately, is unlikely to be the right way to add this....
For reference, the current version (2012-Aug-13) of the patch is: http://nginx.org/patches/spdy/patch.spdy-52.txt and http://nginx.org/patches/spdy/ works to show the list of such patches.
i'd really like to wait for upstream to merge this into nginx. if that is not going to happen in the nearer future, than we can redecide. i'll leave the bug open for now ...
Created attachment 323194 [details] add USE spdy wget http://nginx.org/patches/spdy/patch.spdy-52.txt to ${FILESDIR} at first. stolen from https://raw.github.com/olemarkus/olemarkus-overlay/master/www-servers /nginx/nginx-1.3.1.ebuild
I also have a working ebuild in my overlay: git://people.freedesktop.org/~cloos/overlay.git Cf: http://cgit.freedesktop.org/~cloos/overlay/commit/?id=b86d76ebe4eae25786f9e579 I tried to follow the pattern of the existing additions.
Created attachment 323374 [details, diff] nginx-use-spdy.patch make a patch from Cloos's ebuild, and apply patch in src_prepare() instead of src_unpack().
Looking at http://nginx.org/patches/spdy/README.txt seems that now the SPDY support is provided (rightly) through a nginx_module. So giving that: * the patch is done/supported by the official team of nginx * activating this USE flag is a consciously user choice * we are talking about a development release (so nobody can complain if it's not work as expected) * as Benedict rightly stated: "if that is not going to happen in the nearer future" as it's seem it to me now I think we can put in portage. What you think guys?
Nginx 1.3.15 now incorporates spdy support. Lets work on getting that version in instead. *** This bug has been marked as a duplicate of bug 456224 ***
