| Line 19: | Line 19: | ||
=== Other info: Build Date, Build Host === | === Other info: Build Date, Build Host === | ||
rrpmbuild will be enhanced to fill this information into the package. | rrpmbuild will be enhanced to fill this information into the package. | ||
| + | |||
| + | |||
| + | == Soultions == | ||
| + | === Packages should be installable by zypper === | ||
| + | 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 === | ||
| + | |||
| + | === Requires/Provides === | ||
| + | |||
| + | === Source package creating === | ||
| + | |||
| + | === Other info: Build Date, Build Host === | ||
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 |
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.
When releasing applications, developer may need to change the name, version or other information of the package, we should let them do that.
QtCreator 2.1 supports debian files editing. We can use the same mechanism to implement spec file editing
Enhence rrpmbuild to parse requires/provides from spec file and fill the package with this information.
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
rrpmbuild will be enhanced to fill this information into the package.
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.