Hi Ivan,
I've never actually worked with them, but it seems nice. However, we should
make redirect php://memory and php://temp to php://memory/default and
php://temp/default respectively to avoid break stuff imho.
Cheers,
r1pp3rj4ck
On Thu, Jan 31, 2013 at 10:37 AM, Ivan Enderlin @ Hoa <
ivan.e
Dan, I'm a PHP developer myself too and I always compile PHP and Apache for
my own (PostgreSQL is good for me as it's packaged for Archlinux). But the
majority is just dumb. And you're right about the bug reports, lots of them
would be just like "it doesn't work because of reasons". But they'd at
l
That's what Ralf and I suggested all along. By the way, the problem is
that most of the web developers don't know anything about IT. I guess
most of them use Windows (and you can't expect a Windows user to
compile stuff), and the majority of the other half uses Ubuntu and
never even saw the shell,
This is why I think the best way to deal with the situation is
distributing nightly builds. First of all, we could use the
distributions' make-package files to build the package. And what if it
returns with an error code? Big deal, either no new nightly build on
that day (and report a failure to a
On Tue, Jan 29, 2013 at 6:46 PM, Ralf Lang wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 29.01.2013 18:38, schrieb Pierre Joye:
> > On Tue, Jan 29, 2013 at 6:24 PM, Attila Bukor
> > wrote:
> >> I think Ralf's idea is great. A lot of
I think Ralf's idea is great. A lot of other projects use nightly builds
successfully. I don't think a vbox image would be necessary as no-one
would use nightly builds on a production environment, but if web developers
who feel a little adventurous could add an official PHP nightly-build
repository
