On Sunday 19 June 2011 14:57:38 Kevin Kofler wrote:
> Thomas Olsen wrote:
> > This sounds great. Last year I wanted to make something like this myself
> > [1] only just for scripted DataEngines via OCS, but due to personal
> > circumstancies I was unable to procede with the project.
> 
> To support fetching dependencies from OCS, we will need not only a way to
> handle dependencies (which I'm working on), but also some way to know what
> OCS entry provides the data engine "foo". For distribution packages,
> PackageKit can do the lookup for us (with minor changes which I can base on
> already existing code), but for OCS packages, we probably also need some
> work done on the OCS side. 

Doesn't OCS packages have a unique ID? From the to of my head I was thinking 
of something like:

X-KDE-PluginInfo-Depends-OCS-Package=XXXXXXX

> We'd also have to try both OCS and PackageKit if
> we don't know where a dependency can be found.

-- 
Best regards / med venlig hilsen

Thomas Olsen

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel