[csw-maintainers] php5 packaging

[Mike Watters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Walton wrote:
> Hi All,
> 
> I updated a box that uses php5 today, so I got the new versions that
> were just released.  After bringing the webserver back online, the
> hosted app wasn't responding with anything but the logs showed the
> requested being handled.
> 
> Turns out that since many of the modules that used to be part of the
> core php5 package (session being the one that got me) are now separate
> packages, I simply needed to pull them in and I was back up and
> running.
> 
> I was just wondering if there is a better way to handle situations
> like this...a user doing a 1:1 update of packages will have less
> functionality after the update than they did before.  I think the
> changes are ok overall, but the user interaction may not be.
> 
> Thoughts?
> -Ben
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers

I didn't think about that part of the upgrade.
I wrote admin scripts to gracefully handle the php.ini files.
The new packages do not overwrite the existing php.ini.

There are a couple ways to handle this I think.

examine the existing php.ini file for enabled extensions:

1) kick off a pkg-get -i for each extension that is enabled.
2) display a note to the user to add the extra packages themselves.

This does not account for anything that was previously compiled
statically I am not sure if there were any.

- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoAgxUACgkQLrhmsXMSLxdrKwCeLejN1qO1q2DjHl900VI1tD66
FgEAnR5LcHsyslNKgzfy8U85Qq7GK8m3
=8HRD
-----END PGP SIGNATURE-----