Thanks Rob. Basically I have started by going for the 80-20 rule - as is this should eliminate most of the installation prereq issues I see here. Getting it into the Oracle installer is a little more difficult. We'll still be maintaining the notes which document the required packages - this rpm is a physical manifestation of them, and also acts as a 'truth test' for the notes.
Cheers Damian -----Original Message----- From: Rob van der Heij [mailto:[email protected]] Sent: 23 April 2010 08:44 To: [email protected] Subject: Re: Oracle 10.2.0 Install On Fri, Apr 23, 2010 at 9:22 AM, Damian Gallagher <[email protected]> wrote: > Announced yesterday at the SIG: > > Now available for s390x - Red Hat 5 and SLES 10 - an RPM to check that > software prerequisites are met before Oracle software is installed. It > doesn't contain or install any executable of itself, but the rpm install > process will perform updates to software components if required, or install > missing rpms, depending on the options chosen. We'll be maintaining this as > the OS components change. Please refer to Note 1086769.1 for full details, > and send me any feedback or problems. Cute idea! Will certainly avoid some of the problems mentioned when the dependency checks are there. It will also warn the customer when he's about to remove or change required packages. All that the installer (and maybe the startup routine) has to do is check for the "oracle-prereqs" package to be installed. You probably also need to document the actual packages that provide those components, since the RPM messages give little help there. At least with YaST such intelligence is hidden in some proprietary catalog that will walk the chain of requirements. I understand Novell also has a build service where they take your "oracle-prereqs" package and integrate it with the product (so YaST can find all the required packages). That would let the customer also install it (plus dependencies) from YaST in one go. I could also see some elegance in shipping a bootstrap for the installation program or startup scripts with it. That has the advantage that RPM identifies the pieces of the application that were planted at various places in the file system (outside the /opt/whatever directories). But you probably considered that already. Some products actually invoke the installer from the post-install script, but that is rather annoying (and beyond what the scripts are allowed to do). Rob ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
