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

List:       kde-core-devel
Subject:    Re: RFC: Creation of a new KDE SC module [kdeplugins]
From:       Andriy Rysin <arysin () gmail ! com>
Date:       2010-10-10 19:18:20
Message-ID: 3C0ED1CA-5905-4B87-8EBF-7D71042204BA () gmail ! com
[Download RAW message or body]

On Oct 10, 2010, at 14:41, Alexander Neundorf <neundorf@kde.org> wrote:

> On Sunday 10 October 2010, George Kiagiadakis wrote:
> > On Sun, Oct 10, 2010 at 5:11 PM, Dawit A <adawit@kde.org> wrote:
> > > On Sun, Oct 10, 2010 at 3:40 AM, Sune Vuorela <nospam@vuorela.dk> wrote:
> > > > Currently konqueror-plugins are released in extrager, which is quite
> > > > okay.
> > > 
> > > Then you completely missed the entire point of this discussion. It is
> > > "not quite okay" they are in extragear because it is a complete
> > > maintainence nightmare. Please read the discussion links I provided
> > > above. The plugins, at least as far as konqueror ones are concerned,
> > > need to be versioned the same way Konqueror does. However, the plugins
> > > themselves are "optional" (not needed to run Konqueror) and hence are
> > > located outside of Konqueror's source tree.
> > > 
> > > The idea behind creating this new package/module just for plugins is
> > > to ensure that they are part of the normal branching and tagging cycle
> > > such that we do not have to worry about which version of the plugins
> > > goes with which version of the application. kdeplugins is intended to
> > > be a place to add all plugins that benefit from this.
> > 
> > And why not just put the plugins in kdebase together with konqueror
> > and just make their directory optional with
> > macro_add_optional_subdirectory() in CMakeLists.txt? I don't see why
> > they need to be separated. They can be together and still be optional.
> > Packagers will take care of having them in a separate optional
> > package. If you want them to be released together with konqueror, then
> > the best place is there. Having a kdeplugins module with random
> > plugins for various applications doesn't make much sense to me. And as
> > far as I understand, there are no other plugins to be put in this new
> > module, it's just for the konq plugins, isn't it? All other
> > applications ship plugins together with the application... see kate,
> > ktorrent, kdevelop, kopete, etc...
> 
> Having them separate might make it easier for others to write new plugins. 
> They don't have to build all of kdebase, but only the plugins module.
We could also go the other way and allow building just a parts (submodules) of \
kdebase, then not just plugin developers can benefit the modularity

Andriy


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