Development query concerning software collections
Issue
- We have an application delivered as an RPM which is using PostgreSQL 8.4 as a database backend on Red Hat Enterprise Linux 6.6.
- With our current setup, we have specified a dependency from our rpm to postgresql-server >= 8.4.20 and as a result when our rpm is installed, postgresql-server and any required packages are installed.
- We would like to upgrade our application/rpm to use PostgreSQL 9.6 from the RHEL 3.0 software collection.
- Is it OK to add a dependency from an rpm to the PostgreSQL 9.6 software collection (rh-postgresql96 >= 3.0) in the same way as described above?
- The Red Hat documentation on software collections state the following: https://access.redhat.com/documentation/en-us/red_hat_software_collections/3/html/3.0_release_notes/chap-usage#sect-Usage-Deploy
In general, you can use one of the following two approaches to deploy an application that depends on a component from Red Hat Software Collections in production:
• Install all required Software Collections and packages manually and then deploy your application, or
• Create a new Software Collection for your application and specify all required Software Collections and other packages as dependencies.
- The documentation specifically states to deploy your application as a software collection and specify all required software collections. However we wish to continue deploying our application as an rpm.
- Is it OK to add a dependency from an rpm to a software collection.
Environment
- Red Hat Software Collections
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.