Seems like PHAR causes quite unexpected things, f.e.
http://bugs.php.net/bug.php?id=46194 where PHP crashes if file does not
exist. Please, can this crap be disabled by default (ALWAYS) and only
those who actually need it can enable it?
--Jani
Hello Jani,
we're in alpha and fix all of those issues.
in contrast to 99.9% of our users it is very easy for you to disable it.
But the majority will only get the extension when we enable by default. And
it is one of the big plans for 5.3 to finally support native packaging to
make a lot of things easier. Once again if you don't like it, just disable
it like you configure any of your installations specifically for your
needs - others cannot.
marcus
Monday, September 29, 2008, 1:15:16 PM, you wrote:
Seems like PHAR causes quite unexpected things, f.e.
http://bugs.php.net/bug.php?id=46194 where PHP crashes if file does not
exist. Please, can this crap be disabled by default (ALWAYS) and only
those who actually need it can enable it?
--Jani
Best regards,
Marcus
Top posting since you started it.. :)
Yes, I do disable everything I don't need. You don't need to lecture me
about that. I was just pointing out that this ext/phar/ seems to do
things most enabled by default extensions don't do. Like affect the very
core of PHP. So enabling such by default isn't very good idea IMO..
And this extension was sneaked in core by promising something along the
lines of 'it will not be enabled by default'...iirc..
--Jani
Marcus Boerger wrote:
Hello Jani,
we're in alpha and fix all of those issues.
in contrast to 99.9% of our users it is very easy for you to disable it.
But the majority will only get the extension when we enable by default. And
it is one of the big plans for 5.3 to finally support native packaging to
make a lot of things easier. Once again if you don't like it, just disable
it like you configure any of your installations specifically for your
needs - others cannot.marcus
Monday, September 29, 2008, 1:15:16 PM, you wrote:
Seems like PHAR causes quite unexpected things, f.e.
http://bugs.php.net/bug.php?id=46194 where PHP crashes if file does not
exist. Please, can this crap be disabled by default (ALWAYS) and only
those who actually need it can enable it?--Jani
Best regards,
Marcus
Top posting since you started it.. :)
Yes, I do disable everything I don't need. You don't need to lecture me
about that. I was just pointing out that this ext/phar/ seems to do things
most enabled by default extensions don't do. Like affect the very core of
PHP. So enabling such by default isn't very good idea IMO..And this extension was sneaked in core by promising something along the
lines of 'it will not be enabled by default'...iirc..
It can be disabled during beta-phase.
Currently, we should focus on finding bugs and fixing those — that's
what alpha is about. It's easier to do this, if phar is enabled.
--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/
Currently, we should focus on finding bugs and fixing those — that's
what alpha is about. It's easier to do this, if phar is enabled.
Precisely. If phar hadn't been enabled by default we wouldn't know about
this missing check until someone hit it in production!
- Steph
It can be disabled during beta-phase.
Currently, we should focus on finding bugs and fixing those — that's
what alpha is about. It's easier to do this, if phar is enabled.
Exact. That's my idea, too. By enabling by default we get more tests of
at least the basic functionality, maybe not functional tests but more
runs of make test and way more testing of fancy overwrites phar does.
Additionally a /working/ phar is an extremely helpful feature for many
people.
So, if the problems continue we have to disable it (or possibly even
drop it), if it stabilizes well we probably keep it enabled.
Same goes for other stuff newly enabled by default.
johannes
Totally hating to bring this up again (and hijacking this thread), but
can we please enable ext/xsl by default in 5.3? :>
- David
Am 29.09.2008 um 13:24 schrieb Marcus Boerger:
Hello Jani,
we're in alpha and fix all of those issues.
in contrast to 99.9% of our users it is very easy for you to
disable it.
But the majority will only get the extension when we enable by
default. And
it is one of the big plans for 5.3 to finally support native
packaging to
make a lot of things easier. Once again if you don't like it, just
disable
it like you configure any of your installations specifically for your
needs - others cannot.marcus
Monday, September 29, 2008, 1:15:16 PM, you wrote:
Seems like PHAR causes quite unexpected things, f.e.
http://bugs.php.net/bug.php?id=46194 where PHP crashes if file does
not
exist. Please, can this crap be disabled by default (ALWAYS) and only
those who actually need it can enable it?--Jani
Best regards,
Marcus
Totally hating to bring this up again (and hijacking this thread), but
can we please enable ext/xsl by default in 5.3? :>
Only possible when bundling libxslt -> no way.
johannes
hi Johannes.
Totally hating to bring this up again (and hijacking this thread), but
can we please enable ext/xsl by default in 5.3? :>Only possible when bundling libxslt -> no way.
What David meant is to do the same as ext/libxml (and related). It
would help a lot to spread ext/xslt availability.
Cheers,
Pierre
the bug is updated with my comments, i think it's a cgi not phar
issue. can u pls have a look soon?
thanks
NO.
--Jani
David Zülke wrote:
Totally hating to bring this up again (and hijacking this thread), but
can we please enable ext/xsl by default in 5.3? :>
- David
Am 29.09.2008 um 13:24 schrieb Marcus Boerger:
Hello Jani,
we're in alpha and fix all of those issues.
in contrast to 99.9% of our users it is very easy for you to disable it.
But the majority will only get the extension when we enable by
default. And
it is one of the big plans for 5.3 to finally support native packaging to
make a lot of things easier. Once again if you don't like it, just
disable
it like you configure any of your installations specifically for your
needs - others cannot.marcus
Monday, September 29, 2008, 1:15:16 PM, you wrote:
Seems like PHAR causes quite unexpected things, f.e.
http://bugs.php.net/bug.php?id=46194 where PHP crashes if file does not
exist. Please, can this crap be disabled by default (ALWAYS) and only
those who actually need it can enable it?--Jani
Best regards,
Marcus
Jani Taskinen wrote:
Seems like PHAR causes quite unexpected things, f.e.
http://bugs.php.net/bug.php?id=46194 where PHP crashes if file does not
exist. Please, can this crap be disabled by default (ALWAYS) and only
those who actually need it can enable it?
Hi Jani,
Classic overreacting, and disrespect to years of careful work.
First of all, this bug has existed for all of 10 hours, and the problem
is easy to fix, and caused because I never imagined PHP would be stupid
enough to pass in a null pointer to zend_compile_file (kind of hard to
compile a file whose name is undefined).
This is a 3-line fix, and is only caused by a bug in the CGI handler
coupled with lighttpd, which is setting filename to 0x0, something none
of the other sapis do when a file is non-existent.
Let's think about this for a second: why pass in a null pointer for a
filename to a function whose purpose is to compile a file in the first
place?
How about we disable the CGI sapi under lighttpd by default?
Don't be such a weenie.
Greg