On Thu, 15 Jun 2006 at 00:36, Pascal Bleser wrote:
Adrian Schröter wrote:
You could even add a "Requires: jabberd_backend" to the main package, so the user gets a popup from YaST to select one.
+1
That dependency would be bogus, because the backends that don't have external dependencies will of course stay in the main package, and so the main package would be self-contained. So the difference between this and my solution would be: This: 1. Install jabberd 2. Install the client library package of the database you want to use (if it isn't there already). 3. Configure jabberd to use that database. 4. Find out that jabberd doesn't work. 5. Investigate and find out that a plugin is missing. 6. Search for the package that has the plugin and install it. 7. Enjoy a working jabberd installation. My Solution: 1. Install jabberd 2. Install the client library package of the database you want to use (if it isn't there already). 3. Configure jabberd to use that database. 4. Enjoy a working jabberd installation. I know that this solution isn't perfect either, because it e.g. doesn't cover the case that the installed version of the database client libary might be incompatible with the one the plugin was linked against. I think an ideal solution for this (so that package cluttering is avoided but not too many dependencies are skipped) would be if RPM provided a way to specify, "The dependencies of this shared object are weak. The package will work fine when they are not resolved, but tell the user that he will get this and that additional functionality when he choses to resolve them." cu Reinhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging-help@opensuse.org