Meego Wiki
Views

SDK/Docs/1.0/Packaging MeeGo applications

From MeeGo wiki
< SDK | Docs | 1.0(Difference between revisions)
Jump to: navigation, search
 
(One intermediate revision not shown)
Line 9: Line 9:
* An archive of files to be installed on the destination filesystem (such as executables, images, documentation)
* An archive of files to be installed on the destination filesystem (such as executables, images, documentation)
-
This [[Packaging/Tutorial]] will give you a whole story to create a rpm package from a qt project.  
+
This [[SDK/Docs/1.0/Packaging/Tutorial]] will give you a whole story to create a rpm package from a qt project.  
<!-- To create an RPM package, you need??? -->
<!-- To create an RPM package, you need??? -->

Latest revision as of 15:31, 6 January 2011


To distribute an application to a MeeGo device, it should be packaged using the RPM format. (It is possible to manually copy binaries to a device and get them to run, but this is not recommended, as there is no way to specify dependencies.)

An RPM file is a binary file consisting of:

  • A signature to verify the origin and integrity of the package
  • Metadata (name, version, architecture, authors, etc.)
  • An archive of files to be installed on the destination filesystem (such as executables, images, documentation)

This SDK/Docs/1.0/Packaging/Tutorial will give you a whole story to create a rpm package from a qt project.

References for packaging :

Retrieved from "http://wiki.meego.com/SDK/Docs/1.0/Packaging_MeeGo_applications"
Personal tools