Meego Wiki
Views
From MeeGo wiki
< SDK(Difference between revisions)
Jump to: navigation, search
(Created page with "== Feature proposed == === QtCreator should support spec file editing === Currently QtCreator supports debian files editing. We can use the same mechanism to implement spec file…")
(categorise, wikify section headings)
 
(15 intermediate revisions not shown)
Line 1: Line 1:
-
== Feature proposed ==
+
As MeeGo's default package management system is based on RPM, MeeGo SDK chooses to RPM as the packaging format for deployment and App store uploading.
-
=== QtCreator should support spec file editing ===
+
-
Currently QtCreator supports debian files editing. We can use the same mechanism to implement spec file editing
+
-
 
+
== Packages should be installable by zypper (BMC#11828) ==
-
=== Packages should be installable by zypper ===
+
'''Description'''
 +
<br/>
 +
App store clients will most probably use zypper to install applications, so the RPM created by SDK packager should be able to installed by zypper. <br/>
Currently zypper can't install the rpm generated by rrpmbuild. We must debug into zypper and rrpmbuild to see what's the problem.  
Currently zypper can't install the rpm generated by rrpmbuild. We must debug into zypper and rrpmbuild to see what's the problem.  
 +
<br/><br/>
 +
'''Solution'''
 +
<br/>
 +
After thorough debugging into zypper, Qiang Zhang and I found that zypper expect binary RPMs cantain the sourcerpm tag. So the solution is very simple: add the sourcerpm tag for the binary rpm.
-
=== Requires/Provides support ===
+
== QtCreator should support spec file editing (BMC#12046) ==
 +
'''Description '''
 +
<br/>
 +
When releasing applications, developer may need to change the name, version or other information of the package, we should let them do that.
 +
<br/><br/>
 +
'''Solution '''<br/>
 +
QtCreator 2.1 supports debian files editing. We can use the same mechanism to implement spec file editing
 +
 
 +
== Requires/Provides (BMC#9437)  ==
 +
'''Description '''
 +
<br/>
Enhence rrpmbuild to parse requires/provides from spec file and fill the package with this information.
Enhence rrpmbuild to parse requires/provides from spec file and fill the package with this information.
-
=== Source package creating ===
+
<br/><br/>
 +
'''Solution '''
 +
<br/>
 +
Parse requires/provides in spec file and fill RPMTAG_PROVIDEFLAGS, RPMTAG_PROVIDEVERSION, RPMTAG_PROVIDENAME, RPMTAG_REQUIRENAME,RPMTAG_REQUIREVERSION, RPMTAG_REQUIREFLAGS properly.
 +
 
 +
== Source package creating (BMC#12047) ==
 +
'''Description'''<br/>
 +
GPL enforces us to provide source code. Generating source rpm is an convenient way to fulfil this requirement  <br/>
rrpmbuild will be enhanced to generate source rpm
rrpmbuild will be enhanced to generate source rpm
-
=== Other info: Build Date, Build Host ===
+
<br/>
-
rrpmbuild will be enhenced to fill this information into the package.
+
<br/>
 +
'''Solution '''
 +
<br/>
 +
 
 +
* type field in lead should be 1 to indicate it is an source rpm
 +
* sourcerpm tag should not be filled as it is only for binary packages.
 +
* file list is parsed from SourceX and PatchX tags.
 +
 
 +
== Other info: Build Date, Build Host (BMC#12048) ==
 +
'''Description '''
 +
<br/>
 +
rrpmbuild will be enhanced to fill this information into the package.
 +
<br/>
 +
<br/>
 +
 
 +
'''Solution '''
 +
* RPMTAG_BUILDTIME should be filled with seconds since the epoch at which the package was built.
 +
* RPMTAG_BUILDHOST should be filled with the hostname of the system on which which the package was built
 +
 
 +
[[Category:SDK]]
 +
[[Category:Packaging]]

Latest revision as of 13:20, 12 April 2011

As MeeGo's default package management system is based on RPM, MeeGo SDK chooses to RPM as the packaging format for deployment and App store uploading.

Contents

Packages should be installable by zypper (BMC#11828)

Description
App store clients will most probably use zypper to install applications, so the RPM created by SDK packager should be able to installed by zypper.
Currently zypper can't install the rpm generated by rrpmbuild. We must debug into zypper and rrpmbuild to see what's the problem.

Solution
After thorough debugging into zypper, Qiang Zhang and I found that zypper expect binary RPMs cantain the sourcerpm tag. So the solution is very simple: add the sourcerpm tag for the binary rpm.

QtCreator should support spec file editing (BMC#12046)

Description
When releasing applications, developer may need to change the name, version or other information of the package, we should let them do that.

Solution
QtCreator 2.1 supports debian files editing. We can use the same mechanism to implement spec file editing

Requires/Provides (BMC#9437)

Description
Enhence rrpmbuild to parse requires/provides from spec file and fill the package with this information.

Solution
Parse requires/provides in spec file and fill RPMTAG_PROVIDEFLAGS, RPMTAG_PROVIDEVERSION, RPMTAG_PROVIDENAME, RPMTAG_REQUIRENAME,RPMTAG_REQUIREVERSION, RPMTAG_REQUIREFLAGS properly.

Source package creating (BMC#12047)

Description
GPL enforces us to provide source code. Generating source rpm is an convenient way to fulfil this requirement
rrpmbuild will be enhanced to generate source rpm

Solution

  • type field in lead should be 1 to indicate it is an source rpm
  • sourcerpm tag should not be filled as it is only for binary packages.
  • file list is parsed from SourceX and PatchX tags.

Other info: Build Date, Build Host (BMC#12048)

Description
rrpmbuild will be enhanced to fill this information into the package.

Solution

  • RPMTAG_BUILDTIME should be filled with seconds since the epoch at which the package was built.
  • RPMTAG_BUILDHOST should be filled with the hostname of the system on which which the package was built
Personal tools