> >However: > >A plugin is *required* for licq to work. If I split it up and only licq-base >gets installed which requires licq-plugin then how will someone know >which plugin to install? Then again, if I split it up into licq-base >and then have it require the default no-KDE Qt plugin then there is no >point in splitting. > Could you not include two plugins in the base file and have a different menu entry for kde versus the rest of the wms? __________________________________________________________________ Get your free Australian email account at http://www.start.com.au
- Re: Re: [Cooker] licq qt-gui plugin question Salane King
- Re: Re: [Cooker] licq qt-gui plugin question Geoffrey Lee
- Re: Re: [Cooker] licq qt-gui plugin questi... Salane King
- Re: Re: [Cooker] licq qt-gui plugin q... Salane King
- Re: Re: [Cooker] licq qt-gui plug... Geoffrey Lee
- Re: Re: [Cooker] licq qt-gui plugin question Stephen Magill
- Re: Re: [Cooker] licq qt-gui plugin questi... Geoffrey Lee
- RE: Re: [Cooker] licq qt-gui plugin q... Aaron Cohen
- Re: Re: [Cooker] licq qt-gui plug... Geoffrey Lee
- RE: Re: [Cooker] licq qt-gui plug... Aaron Cohen
- RE: [Cooker] licq qt-gui plugin question Con Kolivas
- RE: [Cooker] licq qt-gui plugin question Aaron Cohen
