Michal Marek wrote:
Cristian Rodríguez wrote:
Andrés G. Aragoneses escribió:
can I do something similar for requiring mysql OR postgresql? It can be done, however remeber that database servers may reside in a different machine as well.
However, I was expecting that most people that would use RPM for installing the package will be interested in a kind of "default install". For distributed installs in which you want the DB engine in other host it's more usual for the people to do a manual installation because they will need to tweak the configuration. My typical use case for this RPM is: install it, and run out of the box. And that implies that, either if mysql or postgresql are used, my RPM will be in charge of creating the initial database. And that is less doable for the "DB in other host" approach because it would require asking some questions to the user 'a-la wizard' in the moment of RPM installation, and IIRC this is not supported, right? (The only system I've seen that asks you configuration questions when installing packages is apt-get.)
Good point - the package shouldn't require the database _server_, but the client library.
But, as I've explained my targets above, my ideal RPM would consist of one that obligues you to install one of these packages as a strong dependency: a) mysql b) posgresql And, if (a) is selected, also have a sub-dependency to perl-DBD-mysql. If (b) is selected, have a sub-dependency to perl-DBD-Pg. Is that doable with current RPM technology and/or OpenSuseBuildService? Thanks, Andrés -- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org