> And how could the postinstall start the database, if the install is not on > the live system? In case of live upgrade we have seen a lot of errors, where > packages were not trully relocatable. We also had packages > and patches which could not be deployed properly to a jumpstart image. > The package was checking for the architecture and as it was an x86 > jumpstart server, it failed for a sparc package. Same if the package > expects hardware, which is available on the client, but not on the install > server.
But a true relocatable package will also be linked with $ORIGIN, and so far, in my 15+ years of working on UNIX, I have never, not once, seen such a package. Not once! I've only read academic treatises in the documentation on it, but never seen one. So just because a package will be installable via JumpStart (or some other means) on a non-running system, does not make it truly relocatable. And as far as bad package examples you cite, did you go back to the guilty party and bust them for it? Show them what they did wrong? Just because few people can't package, doesn't make it right to go on a crusade with IPS. Because two wrongs don't make a right. _________________________________________________________________ Windows Live™: Keep your life in sync. Check it out! http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009 _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
