On 09/09/2010 01:46 PM, Marius Vollmer wrote:
ext Alexey Khoroshilov<[email protected]> writes:
On 09/09/2010 12:48 PM, Marius Vollmer wrote:
ext Thiago Macieira<[email protected]> writes:
Requiring a .noarch.rpm to wrap around a zip file sounds redundant to
me.
A *.wgt is not just a zip file, it contains some package-style meta data
as well, such as a description, author information, a version, and even
'feature requirements', which resemble dependencies:
http://www.w3.org/TR/widgets/
Thus, a *.wgt can be automatically repackaged as a *.rpm. We do this in
Harmattan, and it seems to generally work ok.
This automation can be done either on client side as part of
installation process or on server side within app store. I guess you are
speaking about server side transformation?
Both, actually. It is best done on the server (or even in the developer
SDK), and the package management of the device doesn't even know that
the package used to be a wgt.
It can, however, also be done on the device, when installing a random
wgt from the a web site.
This is the equivalent of installing a random rpm from a web site, which
isn't such a good idea, but the web widget people keep telling me that
it is important for web widgets. *shrug*
In this case, MeeGo specification have to require from compliant system
to be able to install wgt packages keeping system package manager
informed about all details (i.e. the fact of installation and files
installed). On the other hand, WRT MeeGo compliant applications can be
packaged either in rpm or in wgt packages.
And we still need to identify what are requirements to MeeGo compliant
wgt packages as well as what are requirements to MeeGo compliant WRT
runtime and WRT applications.
Alexey Khoroshilov,
ISPRAS / Linux Foundation
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
