Hi, On Tue, 13 Jun 2006 at 15:05, Marcus Rueckert wrote:
imho we have way to many of those "fat pull in all dependencies" packages.
True, that's why I am skipping the dependencies in this special case.
what happens in your jabber package if the required library for a plugin isnt found?
You get an error message saying exactly that. I think that's acceptable, because you have to go through a number of config files when setting up jabberd anyways, and when you decide to use database X as your storage backend you most probably have the respective library package installed already, because for most databases you also need the command line client (which in turn depends on the library) to initialize the database before jabberd can use them. In addition the package contains a README.SUSE file that explains which library packages are needed the respective database backend plugins. I agree that this is nothing for entry level users, but entry level users most probably won't try setting up a Jabber server either. If we wanted to make jabberd ready for entry level users, we'd need a YaST module for it, that asks the user which database he wants to use and makes sure that the needed packages get installed. Again, no RPM-level dependencies needed for that.
imho the dependencies are the way to solve this. and just making rpm blind for those dependencies is an ugly hack.
The dependencies are just a tool. Tools are there to be used when they are helpful and not to be used when they do more harm than good. cu Reinhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging-help@opensuse.org