On Tue, Jul 17, 2012 at 19:38:36 +0200, Evgeni Golov wrote: > 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 > That means licq is now co-installable with plugins from a different version. Why is that OK?
Cheers, Julien
signature.asc
Description: Digital signature
