On Oct 13, 2014 8:08 PM, "Jan Ehrhardt" <php...@ehrhardt.nl> wrote: > > Pierre Joye in php.internals (Mon, 13 Oct 2014 14:21:24 +0200): > >On Oct 13, 2014 7:10 PM, "Jan Ehrhardt" <php...@ehrhardt.nl> wrote: > >> > >> In the ext/mysql case this will be a bit uncomfortable. If you compile > >> PHP --with-mysql=mysqlnd the mysqlnd-part is in core, while a part of > >> the functionality of ext/mysql is used. What if mysqlnd drifts away from > >> supporting ext/mysql? > > > >It is more the other way 'round. > > > >Mysql being not updated to support latest core change. Which may happen, > >and I would have no issue with that if we choose to remove it. > > OK, maybe I should have said 'what if mysqlnd and ext/mysql drift > apart?' But it still feels uncomfortable. Will it be considered a > BC-break if, say, PHP 7.1 changes something in mysqlnd and ext/mysqli > that is also being used by pecl/mysql?
Changes in core happens all the time. It is the responsibility of the external extension maintainers to update their code. That being said, having mysql in pecl should really not mean that its maintainers should keep it alive forever. Users willing (for whatever reasons) to keep using it, can keep using 5.x. But it is not our call, but the maintainers.
