| Line 19: | Line 19: | ||
QtCreator 2.1 supports debian files editing. We can use the same mechanism to implement spec file editing | QtCreator 2.1 supports debian files editing. We can use the same mechanism to implement spec file editing | ||
| - | === Requires/Provides | + | === Requires/Provides (BMC#9437) === |
'''Description ''' | '''Description ''' | ||
<br/> | <br/> | ||
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 |
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.
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
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.
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
Description
rrpmbuild will be enhanced to fill this information into the package.
Solution