Bug#727085: Now we don't depend on the weird libevent patch
>> https://github.com/hhvm/packaging/tree/master/hhvm/deb
> Checked wheezy/ which is just wrong. It's a binary debian directory
>and not a source one, I think 'Essential' is only used if its value is
>'yes'. Standards-Version is missing, no long package description, ...
I would love a pull request, or if you get really into this I'm happy to
make you a co-author on the repo.
>My opinion for releases follows. Do one if there's an important
>bugfix, new feature added, etc. In short, if there's a reason.
>On the other hand, there's no problem with releasing every two weeks,
>it's just not common. It matches with Debian standards, meaning that
>normally ten days needed for unstable -> testing migration.
Excellent. We move pretty fast and are constantly making performance
improvements which is why we release internally every 2 weeks. I'll float
it with the rest of the team. If we do 26 releases this year we'll be at
2.30.0 by the end of the year. Is that weird?
>Do you have a packager position there, at FB? :)
Short term, yes, but long term we would much rather the community take
over packaging.
On my team it wouldn't be a full time job, but I'm filling the role right
now and would love you to do it instead ;) You'd just have to find other
good things to do too. https://www.facebook.com/careers/
>Now my previous package section for HHVM,
>which I've named hiphop-php (to match the PHP policy of Debian, but
>will re-check that):
Our project used to be named hiphop-php when it was a PHP to C++
translator. We decommissioned it in February once the JIT was faster. The
JIT was codenamed HHVM so we've taken that on as the project's main name
since it is the only runtime we support now.
>-- cut --
>Package: hiphop-php
>Architecture: any
>Depends: ${misc:Depends}
>Description: HipHop VM for PHP
> HipHop VM (HHVM) is a new open-source virtual machine designed for
>executing
> programs written in PHP. HHVM uses a just-in-time compilation approach to
> achieve superior performance while maintaining the flexibility that PHP
> developers are accustomed to. HipHop VM (and before it HPHPc) has
>realized
> > 5x increase in throughput for Facebook compared with Zend PHP 5.2.
> HipHop is most commonly run as a standalone server, replacing both Apache
> and modphp.
>-- cut --
Should I use this? Again a pull request would be awesome.
>> I'll probably still have to keep packaging
>> it for other distros since you're only going to do debian, right? Or is
>> there an easy way for you to also do it in other debian-based distros
>> (ubuntu, mint). Can you also do yum based distros or do you know what I
>> should do for inclusion there?
> I think packaging for Debian is a good step. Then Ubuntu maintainers
>will pick it up and as I know, Mint based on Ubuntu, they will have it
>as well. I've experience with Red Hat and Fedora packaging as well.
>You may know that the transition is Fedora -> Red Hat from time to
>time.
I would be elated for any help you can offer here. And even if you can't
do it, guide me on the steps I need to do and I'll do everything in my
power to help. We are very excited about being in every distro.
One other thing I haven't brought up and probably should, is we are trying
to be a drop-in replacement for all facets of php. For example, if our
binary is named "php" then it will accept the same command line args that
php-src accepts. For now, the packages I've made have left our binary
named hhvm since I don't know how it will interact with the php-src
package, but if there is an easy way to use "alternates" or something we
can drop in and replace the system binary too (and give a big speed boost
to user's scripts).
Paul
Reply to: