# Disable PHAR by default

- Thread: https://externals.io/message/40761
- Original archive: https://news-web.php.net/php.internals/40761
- Started by Jani Taskinen on 2008-09-29T11:15:16+00:00
- Messages: 12
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #40761 — Jani Taskinen — 2008-09-29T11:15:16+00:00

URL: https://externals.io/message/40761#40761

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

---

## #40762 — Marcus Boerger — 2008-09-29T11:24:42+00:00

URL: https://externals.io/message/40761#40762 · In reply to: #40761

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

---

## #40763 — Jani Taskinen — 2008-09-29T11:32:08+00:00

URL: https://externals.io/message/40761#40763 · In reply to: #40762

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:
> 
> > […]
> 
> > […]
> 
> 
> 
> 
> 
> Best regards,
>  Marcus

---

## #40764 — Alexey Zakhlestin — 2008-09-29T11:35:24+00:00

URL: https://externals.io/message/40761#40764 · In reply to: #40763

> 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/

---

## #40765 — Steph Fox — 2008-09-29T11:56:28+00:00

URL: https://externals.io/message/40761#40765 · In reply to: #40764

> 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

---

## #40767 — david.zuelke@bitextender.com — 2008-09-29T12:32:43+00:00

URL: https://externals.io/message/40761#40767 · In reply to: #40762

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:
>
> > […]
>
> > […]
>
>
>
>
>
> Best regards,
> Marcus

---

## #40769 — Gregory Beaver — 2008-09-29T13:07:07+00:00

URL: https://externals.io/message/40761#40769 · In reply to: #40761

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

---

## #40770 — johannes@php.net — 2008-09-29T13:15:34+00:00

URL: https://externals.io/message/40761#40770 · In reply to: #40767

> 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

---

## #40771 — johannes@php.net — 2008-09-29T13:19:01+00:00

URL: https://externals.io/message/40761#40771 · In reply to: #40764

> 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

---

## #40772 — Pierre Joye — 2008-09-29T13:24:01+00:00

URL: https://externals.io/message/40761#40772 · In reply to: #40770

hi Johannes.


> 
> > […]
>
> 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

http://blog.thepimp.net | http://www.libgd.org

---

## #40796 — Xuefer — 2008-09-30T02:17:27+00:00

URL: https://externals.io/message/40761#40796 · In reply to: #40772

the bug is updated with my comments, i think it's a cgi not phar
issue. can u pls have a look soon?

thanks

---

## #40811 — Jani Taskinen — 2008-09-30T15:14:24+00:00

URL: https://externals.io/message/40761#40811 · In reply to: #40767

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:
> 
> > […]
