RFC: Creation of a new KDE SC module [kdeplugins]

Dawit A adawit at kde.org
Sun Oct 10 15:11:57 BST 2010

On Sun, Oct 10, 2010 at 3:40 AM, Sune Vuorela <nospam at vuorela.dk> wrote:
> On 2010-10-09, Allen Winter <winter at kde.org> wrote:
>> btw: a module is a logical grouping; a community; a way for packagers and users
>> to differentiate programmatic elements.
> I'm not sure I see the logical grouping of plugins together.
> I see the logical grouping of 'konqueror plugins' together. Or Okular
> plugins. or. or. or.
> But I honestly don't see what a konqueror plugin has to do with a plugin
> for <other app>

That was not the point...

> 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.

> Wearing my packagers hat, I also don't like unlogical grouping together.

You mean like extragear ? By comparison kdeplugins is more logical
since it will only contain plugins specifically grouped by application
and/or module they came from. IOW, it is more saner than the current
situation where applications plugins and everything else in between is
simply dumped into one big repository...

Dawit A.

More information about the kde-core-devel mailing list