On Fri, 4 May 2007, Lukas Kahwe Smith wrote: > Ilia Alshanetsky wrote: > > > > On 4-May-07, at 3:14 PM, Lukas Kahwe Smith wrote: > > > > > Yes, to me the question is only if we want to give the message that > > > software producers should be able to expect phar to be there on 99% of the > > > systems. Thats the only way that phar has a good chance of really taking > > > off as a php code distribution approach. > > > > It sounds like the merits of having phar is would only be apparent after it > > is included in the core and everyone starts using it because of that. This > > won't happen simply because most software producers can't rely on extensions > > that are only available in version X. > > No, the point is that if we want to push something, we need to add it sooner > rather than later, because there will be a delay anyways. Also simply by > putting it into core, we make sure that phar gets into the long terms plans of > users (which are then more likely to accept the transition pain, because they > know its going to be around and maintained).
Right, so the question is whether we want to push it or not. What would be good reasons for adding phar to the core? regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
