Hi, I think the whole licq-plugin stuff is done wrong. Licq clearly needs an additional plugin to be usable, but not all plugins are sufficient: licq needs a ui/frontend plugin to be usable.
Given the following real packages (I droped transitional and common ones): licq - multi-protocol instant messaging client (base files) licq-plugin-autoreply - autoreply plug-in for Licq licq-plugin-console - console user interface plug-in for Licq licq-plugin-forwarder - forwarder plug-in for Licq licq-plugin-jabber - Jabber plug-in for Licq licq-plugin-kde4 - graphical user interface plug-in for Licq using KDE4 licq-plugin-msn - MSN plug-in for Licq licq-plugin-osd - on-screen display plug-in for Licq licq-plugin-qt4 - graphical user interface plug-in for Licq using Qt4 licq-plugin-rms - remote management server plug-in for telnet Licq access I propose the following: * licq depends "licq-plugin-qt4 | licq-plugin-ui" * -console, -kde4, -qt4¹ provide licq-plugin-ui * all (real) plugins recommend(!) and enhance licq * the current -plugin provides becomes useless and can be dropped Regards Evgeni ¹: Not sure if -rms also should provide -ui. Reading the log above it should not. -- Bruce Schneier can read and understand Perl programs. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
