[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Little evaluation of "kioslave location" thread
From:       Matt Koss <koss () post ! sk>
Date:       1999-11-10 21:37:22
[Download RAW message or body]


Because I have brought this topic on, I want to evaluate a bit what came out
from it.

I know that we got to an endless chain, which starts with "Help" button which
leads to khelpcenter, then we need also kcontrol to configure stuff, konqueror
to be able to use links in khelpcenter etc. etc.

I really don't want to put anything to a one huge package, because it would not
solve anything and as time passes by, we would add and add new packages, but
everything depends on everything.

So let's say, that these two packages are both required and that's it.
We should then move file slave back from kdelibs/kio to kdebase/kioslave to
avoid a non-sensical separation.

This solution will probably not be accepted by all users, who won't understand
why they have to install a window manager and file browser, in order to use
only a download manager.

I would see only one other way then, and it is a creation of separate
packages for some apps. Each package would contain only things that are needed.
Even kdelibs package is big, if app doesn't need some libraries like kparts or
libkab ( BTW what apps do really use libkab, except addressbook ? ).
E.g. Caitoo doesn't need all kioslaves, only file, ftp and http slaves.

Creation of these packages could be done by developers themselves, or could be
somehow automated from CVS.

Majority of KDE users will probably simply install kdelibs, kdebase etc
But there are users who want to use only one app and who look closely what gets
installed and who care about a disk space.
This would be a way for them.

Would this be possible ?  Any ideas ?


	Regards

			Matt


-- 
Matej Koss	e-mail: koss@post.sk
Kosice		 ICQ# : 19344305
Slovakia

[prev in list] [next in list] [prev in thread] [next in thread]