Re: where is the kde plugin? - duh

Am Montag, 14. August 2006 14:02 schrieb Arne Schmitz:
> Am Montag, 14. August 2006 13:25 schrieb Dexter Filmore:
> > Well, I prefer having packages, so if I'd rather write a script that
> > merges the main app and plugins in /tmp, should be simple - but in the
> > first place I went for svn because 1.3.2 is so old and lacks quite a lot
> > of functions. Usually I wait for stable releases, usually apps like Licq
> > are released as a Slackware package rather quickly.
>
> Yes, with Slackware that is simple, because you don't have dependencies,
> right? For RPM and DEB packages building separately is easier, because the
> LICQ backend does not depend on either Qt nor GTK. The frontends are
> depending on Qt, GTK or ncurses respectively. So it is easier to build and
> package them separately, I guess.

Build dependencies is one of the good reasons. Another one is, that not 
everybody wants QT-gui. I know people that use licq on server systems without 
X, only console. Those don't want to install X and Qt if only the daemon and 
ncurses would suffice their needs.

In the past i built the SuSE packages for Licq and it is easier to seperate 
gui and daemon. In addition it really is no hassle for the user to select 
"licq-kde-gui" in their package manager and let it resolve the dependency to 
licq-daemon automatically.

Cheers,
Thomas

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642