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

List:       kde-core-devel
Subject:    Re: Little evaluation of "kioslave location" thread
From:       Dawit Alemayehu <adawit () earthlink ! net>
Date:       1999-11-11 3:07:51
[Download RAW message or body]

On Wed, 10 Nov 1999, Matt Koss wrote:
> 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.
> 

My fear with this would be that if developers are allowed to package things 
things they need aribitrarily within thier own apps, then it would be a
maintainance night mare.  What if say I include kioslaves in my app XYZ and
for arguments sake I did not update the kioslaves ( not in sync with the one in
CVS ).  As a result I end up overwriting any newer slaves the user might have
on his/her machine and in the process stop any apps that relied on the newer
slaves from working.  This has happend to me before. All beit through my own
stupidity.  But IMHO it is something to think about when looking at this type of
alternatives ....

Regards,
Dawit A.

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