As far as I can see there are very few extension that are really needed in
the core, the main problem comes from distributions changing the methods
that PECL works or the core works

e.g.
Ubuntu you need to install the -dev version in order for extension to be
compiled/installed
Gentoo you need to either write your own ebuild for a pecl extension, hope
one exists, or go through lots of hoops to get them to work

the problem we have is getting this across to either distribution builders,
or giving them a set of standards to follow so that the process of building
PECL extensions is easy to follow from the 'user' perspective, you should be
able to follow the install guides on pecl.php instead of searching for your
distributions special method

//
then it comes to things that arent maintained in PECL and then get used, in
those instances, there is an even bigger reason not to incoroprate it into
the core, if something no longer works because it isnt maintained, putting
that into the core is shooting ourselves in the foot, the best thing that
can happen with those extensions, is for you to post a bug report, if there
is no response, it must be dead, and take that as a sign that you need to
re-write your own code

\\
taking the attitude of shouting odds because your view isnt being listening
to, is not the way to go, all you do is alienate yourself, and people are
unlikelly to listen to you, re-evaluate what your trying to say and then
listen to the views of others, you will realize that the view to incoroprate
dead things into the core on the "hope" that it will suddenly start working
is not going to happen,

your best option is to take the mantle, and fork that project, and make it
work, there is proberlly a way of telling pecl that yours is then the one to
use


On Fri, Jun 10, 2011 at 11:50 AM, Lars Strojny <l...@strojny.net> wrote:

> Am 10.06.11 11:20 schrieb "Reindl Harald" unter <h.rei...@thelounge.net>:
>
> >let the api fuck in peace or you risk that the extension will not used
> >in the future because you force all users to totally change their
> >projects with
> >the fear that 5 years later 3.0.0 breaks all baackward compatibility again
>
> Please change your tone.
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Reply via email to