-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK, I've built RPMs of PHP 4.1.2 with Mitel's patch applied (on my
server now; should be on ftp.e-smith.org tonight). However, I'm sure
they're going to conflict with Update 1, as it specifies different
versions of the PHP modules (I don't know for sure, as I haven't been
able to get the update installed yet--high traffic, I suppose).
What's the best way to handle this?
1. Tell people not to install Update 1. I don't much like this, as
I'd be telling people not to use a mitel "Mandatory" update.
2. Install the new RPMs with --nodeps. I don't really like this
either.
3. Add an Obsoletes: tag to the PHP RPM, obsoleting update 1. This
should be neater for the end user, as it'll remove Update 1 behind
the scenes, but it will still (I expect) show as not installed in the
Blades panel. This is the best I can think of at the moment. I'm
concerned, though, that it might interfere with Update 2 if/when it
comes out.
4. Something else?
- --
Dan Brown, KE6MKS, [EMAIL PROTECTED]
"Since all the world is but a story, it were well for thee to buy the
more enduring story rather than the story that is less enduring."
-- The Judgment of St. Colum Cille
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBPIi+mH6CI7gsQbX8EQI5aACeIa4Nc9osrWE30B3/YisuwNOKjb0AnRDf
jNJt8vej+3PjgfpBZdC3LU2C
=E6Ml
-----END PGP SIGNATURE-----
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
