This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
[dev.icinga.com #4517] icinga.spec: different handling of ido2db.cfg in idoutils-libdbi-* packages #1325
Labels
Comments
Updated by mfriedrich on 2013-10-11 10:17:19 +00:00
|
Updated by elagon on 2013-10-11 10:26:52 +00:00 +1 for me |
Updated by mfriedrich on 2014-07-19 13:11:01 +00:00
please have a look. |
Updated by spstarr on 2014-07-20 22:50:24 +00:00
I've adapted this for the Fedora spec file thanks, it is now in. |
Updated by spstarr on 2014-07-20 22:50:47 +00:00
|
Updated by mfriedrich on 2014-07-21 07:58:53 +00:00
1.11.5 is already released, please use 1.11.6 as target version. |
Updated by mfriedrich on 2014-08-06 19:16:57 +00:00
|
Updated by mfriedrich on 2014-10-26 19:12:41 +00:00
|
Updated by mfriedrich on 2015-02-14 16:13:50 +00:00
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/4517
Created by mgruener on 2013-08-06 09:54:49 +00:00
Assignee: spstarr
Status: Closed (closed on 2015-02-14 16:13:50 +00:00)
Target Version: (none)
Last Update: 2015-02-14 16:13:50 +00:00 (in Redmine)
In the current icinga.spec the process to package the ido2db.cfg file for the idoutils-libdbi-* packages is as follows:
idoutils-libdbi-mysql: package as is
idoutils-libdbi-pgsql: package as is, but modify for postgres during post-installation (and do so everytime the package is updated)
This has some disadvantages:
I would like to propose the following procedure to handle the ido2db.cfg file
This approach should circumvent the aforementioned disadvantages.
I have attached a patch containing the necessary changes.
Attachments
The text was updated successfully, but these errors were encountered: