[ECODP-dev] ODP - Onsite Workshop on RPM packages for software deliveries

Bert Van Nuffelen bert.van.nuffelen at tenforce.com
Wed Jan 30 10:17:36 UTC 2013


Hi Olivier,

here is a list of questions I have compiled for next week.

Questions

*  In Ubuntu installing packages is done with superuser rights.
   So far the EU ODP installation instructions where "be root and than
execute yum install <package>"
   Is this instruction still valid?
   Is yum the package manager to be used?

*  If the package has to install under a non-default location under a
non-default user what is the
   install command?

*  how does that work for RedHat packages such like apache, tomcat.

*  suppose Redhat issues an security patch for apache, tomcat is the
rpm management capable of
   dealing with the "non-default" locations/configurations?

*  A EUODP rpm package has dependencies: how do you specify them.

*  In Ubuntu if you request the installation of e.g.

        sudo apt-get install ckan

   then the apt package manager investigates the dependencies and
proposes to install
   these accordingly.
   However these are installed in the default locations.

   How does this work on RedHat, and how is dealt with the requirement
to install dependent
   software also in non-default locations.

*  is there an equivalent to debhelper in redhat?

*  which of the scripts should be written minimally, which are optionally

*  the current installation scripts aid in setting the right
configuration values based on a single
   global configuration file.

   How is this supported by the rpm build scripts?

   How to ensure that individual installation leads to a connected application?

*  How to deal with PO local changes to the configurations values on
reinstalling a new version?
   E.g. memory changes, proxy ip-address, pwd

*  How to enter passwords in the configuration process?

*  is there support to create packages from java code?

*  how to create packages from binary sources?

*  how to create packages for software source?

*  If a package requires changes in the configuration of another
package to create a connection between the 2 components.
   E.g. the current install script for solr updates the tomcat base
configuration.
   How can solr update the tomcat configuration if it does not know
the location of the configuration. As this location is
   is non default.




This covers part to increase the understanding on how the PO will
install the software and
how to build the rpm, which I see is one element of the whole process.

Bert

-- 
Bert Van Nuffelen

Semantic Technologies Software Architect at TenForce
www.tenforce.be

Bert.Van.Nuffelen at tenforce.com
Office: +32 (0)16 31 48 60
Mobile:+32 479 06 24 26
skype: bert.van.nuffelen




More information about the ecodp-dev mailing list