Plasma ScriptEngines and plasmapkg to kdebase/runtime?

[Allen Winter]

On Thursday 07 May 2009 1:13:51 pm Aaron J. Seigo wrote:
> hello...
> 
> we have received requests from non-workspace-application developers[1] using 
> libplasma to move the ScriptEngines[2] and the plasmapkg[3] utility somewhere 
> they can get at them without inheriting a(n unwanted) dependency on kdebase-
> workspace.
> 
> since they are not build requirements, kdebase-runtime seems like the natural 
> place for them.
> 
> any questions / concerns / thoughts / flames / cookies / European swallows[4]?
> 
To summarize, you want to move:
kdebase/workspace/plasma/scriptengines to kdebase/runtime/plasma/scriptengines
kdebase/workspace/plasma/tools/plasmapkg to kdebase/runtime/plasma/tools/plasmapkg

right?

Seems a fine idea to me.
I don't see any obvious dependencies in there to prohibit  such a move.



> 
> [1] Amarok is probably the most recognizable name there; they are motivated by 
> the desire for JavaScript based scripting features in Amarok2
> 
> [2] ScriptEngines allow one to write plasma addons (plasmoids, DataEngines, 
> runners) in languages other than C++ and ship them as tidy little packages
> 
> [3] plasmapkg allows one to install / remove / upgrade a packaged addon, e.g. 
> a plasmoid, specific to an application. it's not a replacement for things like 
> rpm/dpkg/etc or apt/zypper/yum/etc, it just covers the much more mundane task 
> of post-system-installation non-binary (scripts, wallpapers, etc..) 
> application addon management
> 
> [4] we're not interested in African swallows, as they have a completely 
> different load tolerance profile.
> 
> 

-- 
Allen Winter | allen at kdab.net | Software Engineer
KDAB (USA), LLC, a KDAB Group company
Tel. USA +1-866-777-KDAB(5322), Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-independent software solutions