On Aug 15, 2008, at 8:34 PM, Ryan Schmidt wrote:
An alternate way of handling this would be to make the oracle- instantclient port an empty port that just depends on either the PPC or intel version of the client (which you would make new ports for).How do I handle upgrading from the current port to that? If oracle- instantclient is changed to depend on oracle-instantclient-intel, say, and oracle-instantclient-intel installs the files that are currently installed by oracle-instantclient, then MacPorts will try to install oracle-instantclient-intel first before uninstalling the old oracle-instantclient and it'll have an activation error because the files are still there.
I don't know of a good way of doing it.I think it's preferable to suffer some immediate pain (with ui_msg instructions to tell people to uninstall the old instantclient) in order to get it fixed, though.
You could also change where things get installed so that the platform- specific instantclients don't conflict with the current port, but that's probably not a great solution.
-- Daniel J. Luke +========================================================+ | *---------------- [EMAIL PROTECTED] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
