Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=693608 Michael Friedrich <michael.friedrich@xxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael.friedrich@xxxxxxxxx | |.at --- Comment #7 from Michael Friedrich <michael.friedrich@xxxxxxxxxxxx> 2011-06-03 09:07:43 EDT --- > Idoutils are provided for mysql, postgresql and oracle. If it is build with > --enable-idoutils like in the spec it is build for use with mysql. If > --with-pgsql is also added it is build for postgresql. --with-oracle would > build for oracle but needs ocilib or oracle instant client, both not use able > for build because of licensing. > See: http://docs.icinga.org/1.3.0/en/quickstart-idoutils.html allow me to correct that as I am the developer who added the --enable-pgsql flag in order to use libpq instead of libdbi's abstraction layer for postgresql. current implementation of idoutils focuses on 2 dependencies, which are used productively and are fully implemented: * --enable-idoutils needs libdbi, whereas you can load either libdbd-mysql or libdbd-pgsql as a rdbms driver being detected as approriate. so this flag as is will provide *either* mysql *or* pgsql - no further configure option needed during build * --enable-idoutils --enable-oracle requires ocilib as oracle rdbms abstraction layer. as there are no builds available, i have created a spec file myself in order to ship that in our environment. https://wiki.icinga.org/display/Dev/ocilib but due to the dependency on commercial, not fully licensed rpms (oracle instantclient) this can't be built into by default. so this was made an exclusive configure option for those demanding a seperated build (gcc will create another binary, ido2db.cfg will need an adapted config whilst depending on tnsnames.ora and such. > > I can see the difficulties in building both mysql and postgresql support, but I > think it would be good to do so and split idoutils in three packages: > - idoutils providing the common files > - idoutils-mysql providing the files for mysql > - idoutils-postgresql providing the files for postgresql > and delete the oracle specific files. that sounds good to me, but keep in mind that rpmforge spec file (which is the default we provide within the official Icinga tar.gz) already built - icinga-idoutils (for libdbi usage with mysql and pgsql) - icinga-idoutils-oracle is never found anywhere, but can be contributed somewhere for those needing it (e.g. Icinga Wiki) Even though, to conclude with the original discussion - my packaging skills are work-in-progress, especially on rpmlint/selinux. So if you have any suggestions especially for RHEL/Fedora on the spec file which could fit to upstream (side-by-side for SuSE), then feel free to get in touch. Either open a new issue on the dev tracker, get aboard the mailinglists or join the IRC community - https://dev.icinga.org https://www.icinga.org/support Kind regards, Michael -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review