Description of problem: Support of different database backends requires split of database specific code to independent setup scripts. Otherwise we will install unnecessary drivers/scripts via rpm dependencies. Version-Release number of selected component (if applicable): Spacewalk 0.7 How reproducible: Steps to Reproduce: 1. choose one of database backends (oracle o postgresql as of now) 2. install spacewalk 3. check that no other database backend packages/scripts/files have been installed (e.g. via rpm -q) Actual results: both oracle and postgresql packages are installed: oracle-instanclient-basic oracle-instanclient-sqlplus cx_Oracle postgresql-jdbc postgresql-libs python-pgsql Expected results: successful installation only drivers for selected db installed Additional info:
Mass-moving to space13.
Michael, this is already solved, isn't it? Can we close this one?
Nope, it's not finished yet.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
I'd consider this resolved. With the spacewalk-sql script and the spacewalk-oracle and spacewalk-postgresql packages, you choose the the supported backend during installation. Yes, in pacewalk-setup and Spacewalk::Setup, we have a mix of functions for both databases and we might get to split that out eventually, but right the installation works just fine so I propose closing it as CURRENTRELEASE. Do you concur?