On 2014-10-29 15:07, Baptiste Daroussin wrote:
On Wed, Oct 29, 2014 at 05:03:49PM +0400, Slawa Olhovchenkov wrote:
On Wed, Oct 29, 2014 at 01:53:04PM +0100, Baptiste Daroussin wrote:

> > > How can we know pecl-memcache has to be reinstalled?
> > >
> > > We won't reinstall each time a version of a dep changes :)
> >
> > And what is solution?
> > May be some flag on package (php) for reinstall all deps?
> I do have no idea, I'm open for suggestions :)
> Either on the package side with triggers but that means implementing trigger 
> package
> Or in package side with provide/requires saying that this packages requires an
> exact version of php meaning in case of upgrade of php the version would have
> changed

May be (as workaround) some database witch this packages?
List, or regexp.

This is need for some binary modules and don't need for "text"
But for some cases -- and for "text" modules too.

> Or someone has to be clever and find a ports only solution.

On ports side pecl-memcache rebuild on php version changed.

> Why the help does a minor version has an inpact on the pecl? isn't the abi
> stable over minor versions?

I am don't know -- I am not php guru.
As result -- memcache module don't loaded and "class Memcache not
May be just strict version check.

From what I do read from here:

only going from X.Y to X.Y+1 needs to rebuild the extensions.
and going from X.Y.Z to X.Y.Z+1 should be compatible

As far as I can tell from my own experience, every time I upgrade PHP, I always have to also reinstall pecl- packages, and even some other things like xcache, xdebug and so on.

Kind regards
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to