Am Sonntag, 17. Juni 2018, 17:39:00 CEST schrieb Stefan Brüns:
On Sonntag, 17. Juni 2018 17:08:40 CEST Axel Braun
we had some days ago a discussion on how to prevent postgres10
as postgres96 is required:
I think you are trying to solve the problem on the wrong level. Obviously,
GH needs postgres in version 9.6, but how this requirement is met is out of
scope for RPM. You can run PG as a local instance on a random, local port.
You can run PG on a remote server or in a container on the same host.
Using update-alternatives is IMHO not an option, as it would change the
system default, but still does not guarantee which database version will be
used, e.g. if not running on the local host.
Both of your points above are true, but I would consider this as 'expert
option' - they know what to do anyway.
The target is to have a system up and running after the installation, with
only minor interaction needed, and without the need to read a postgres-book
This was all achieved out of a single package, but not anymore with postgres10
Probably, you should add a dependency on a
metapackage, and provide
different variants for this dependency:
- one package configuring GH to use a remote PG instance
- one package configuring GH to use a local PG instance, running on a
randomized local port.
Do you maybe have an example?
Thanks for your input
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org