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

List:       kde-core-devel
Subject:    Re: Are there any plans to create a CVS module for plugins ?
From:       Dawit Alemayehu <adawit () kde ! org>
Date:       2001-04-18 23:43:11
[Download RAW message or body]

On Wednesday 18 April 2001 18:30, Cullmann Christoph wrote:
> On Wednesday 18 April 2001 10:11, Cullmann Christoph wrote:
> > Am Mittwoch, 18. April 2001 18:47 schrieb David Faure:
> > > On Wednesday 18 April 2001 17:35, Cullmann Christoph wrote:
> > > > Am Mittwoch, 18. April 2001 15:42 schrieb Cullmann Christoph:
> > > > > Hi,
> > > > > Kate supports now plugins too (like konqueror).
> > > > > Wouldn't it be a good idea to add a cvs module kdeextra or
> > > > > kdeplugins for konqueror (which are located at kdenonbeta) kate and
> > > > > any other plugins (perhaps extra kcontrol center modules )?
> > > >
> > > > If we call it kdeextra or kdeplus it would be the right place for
> > > > extra kioslave and such things.
> > >
> > > Since I only suggested this privately, I want to said publically that I
> > > support this idea.
> >
> >I was told to offer my support for this idea. So I vote for "kdeaddons".

Hi,

I guess I will be the lone dissenter then on this issue.  My primary problem with this is 
that all that is being changed is that some of the non-essential, but perhaps useful
packages are all being lumped together into one large package.  This is probably
very convenient from our (developer/maintainers) point of view.  Specially for the
person responsible for this package.  However, I cannot see how this is going to
benefit the user who just wants to say get one of the konqueror plugins ?  

(S)He will be forced to download the whole package just to get a single io-slave or 
plugin or whatever.  This has been one of the biggest complaints by users about 
upgrading KDE and the reason I was asking for putting all the io-slaves into one package
on its own and asking user to download it separately.  For example, kdelibs can come
only with the file io-slave and all the others will be packaged into two other kioslave 
packages, kioslave-basic and kioslave-extra or some similar name.  Then we can put
ftp, http, pop, man, help and any other io-slaves to be used by most people into 
the basic package and remaining ones will go into the kioslave-extra package.

I know the above setup will mean new dependencies for packagers and probably a
PAT to originally adapt, but it will be mostly beneficial to the end user as (s)he will only
need to update the necessary package for bug fixes in io-slaves or plugins or new icons
or wallpapers etc etc.  Anyways, what I am getting at is that packaging addons or 
non-essential plugins etc into one large package IMHO is the wrong approach. 

Just my $0.02 worth.

Regards,
Dawit A.

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