From Ingres Community Wiki

Building an OS/X native installers will require several items:

• Determining the proper raw packaging. For example, should the Mac package file contain the normal, existing tar files?
• Deciding on if/how to use the existing installer with a response file
• Building the wrapper of any internal Ingres bits with an Xcode based install tool

You must not be required to have system administration privileges to install and run Ingres with the default install configuration. A restart must not be required.

Package Identifier: com.ingres.pkg

The installer will have a simple install mode and an advance install mode.

• Simple mode will be the default. It will provide the basic Mac standard "Just this user" and "everyone" as the default choice and will install using with admin rights an "all users" selection where II_SYSTEM=/opt/Ingres/IngresII by default. If the user wants a "just this user" install the default location will be ~/Ingres/IngresII The installation code should remain II to provide the best compatibility with existing documentation, particularly with respect to URL definitions for JDBC access.
• In advanced mode the user should be able to select a specific value for II_SYSTEM and custom definitions of II_DATABASE, II_CHECKPOINT, II_JOURNAL, II_DUMP, II_WORK, and II_LOG_FILE. It should also allow a custom installation code and the specification of a different log file size. It will not, during installation, allow dual log to be specified or a default date format of ingresdate. (There needs to be a documented way to reverse that after installation). Everything else can be configured later, including the number of supported users.

The installer must determine the port number for the DAS server and prompt the user for permission to open that port on the firewall. The user disallowing the port to be open should not cause install failure. GCC should be installed but turned off (??) by default.

The timezone and number of processors should be automatically calculated.

Optionally add (if missing) the appropriate environment variables to ~/.macosx/environment.plist (??) Do not overwrite anything that already exists. Only do this for an advanced mode install. We should probably see if we can figure out a "Terminal.app" configuration that would launch a command line window for that installation; much like the Windows environment uses;

Produce a preferences control panel (see MySQL for an example) to manage one or many Ingres installations and have that preferences panel installed by the installer. Preferences should be optionally installed as either user local (~/Library/PreferencePanes) or system wide (/Library/PreferencePanes).

Tools: PackageMaker (/Developer/Applications/Utilities/PackageMaker.app by default)

All of the Ingres files should be placed into the $II_SYSTEM directory. However, the installer should enable only the following executables to activate during Ingres startup:

 iigcn (the name server)
 iidbms, dmfrcp, dmfacp  (the "core" of the dbms)
 iigcd (the DAS server - JDBC and .NET support)

In the not sure category:

 ODBC

Install, but to set the startup count to 0:

 iigcc (Do any Mac realm users care about Ingres/NET by default?)
 STAR
 Bridge Servers

Do not install:

 Web Deployment Option (was: ICE)

By default, the Mac Ingres install should use

 II_GC_PROT=UNIX
 II_GC_PORT=$II_SYSTEM/ports/

By using this approach, we will not have to worry about firewall settings for the name server and database engine. We also don't have to worry about Mac OS prompting users for firewall settings during server startup.

(The discussion page for analysis, questions, and conjecture is active)

Project Members: Daryl Monge Mike Hjorleifsson