I'd like to revive this bug now that our libevent plans are solidified. With our 2.3.0 release we now support FastCGI and we want to make that the default method to run HHVM. Our FastCGI server works with the standard libevent 2.0 library and if that is the only thing present on the compiling machine, then the standalone HTTP server support won't be available and you can only use FastCGI. This is the mode we expect to become the default with a future release (probably 2.5.0 in 4 months).
What else should I be doing to get this packaged up for inclusion in debian? My method of packaging our release is very clowny (I compile the binary and then copy it into a directory with the skeleton for the package and then build that with dpkg -b) so I'd rather someone else with more debian experience build a proper package for us. You can find me on IRC on freenode in #hhvm if you prefer real-time. Paul -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ced497e6.565ef...@fb.com
