The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Packaging/Ruby
(→Packaging with gem2rpm) |
|||
| Line 21: | Line 21: | ||
/usr/share/gems/bin/gem2rpm <mygemname-version>.gem > rubygem-<mygemname>.spec | /usr/share/gems/bin/gem2rpm <mygemname-version>.gem > rubygem-<mygemname>.spec | ||
| − | + | After the .spec file is created next thing is to check if there are any hacks needed that needs to be preserved. | |
| + | |||
| + | When the possible modifications are done it is time to add files, add new entry to .changes file and upload the new packaging. | ||
... | ... | ||
[[Category:Packaging]] | [[Category:Packaging]] | ||
Revision as of 13:32, 9 July 2012
Draft
Ruby is used mainly for Testing and Tools in Mer and thus it is going to Mer:Tools project in community OBS. As ruby consists of numerous different gems, a packages that contain ruby libraries or applications, there is need for consistent policy how we should package them.
Package Naming
ruby gems packages should hae follow prefix in package names: rubygem-
Packaging with gem2rpm
First start by installing Mer SDK. After that is done login to the SDK and install rubygem-gem2rpm
sudo zypper install rubygem-gem2rpm
After that is done you need to fetch the gem you want to package.
gem fetch <mygemname>
When the gem is downloaded you can create .spec file with following cmd
/usr/share/gems/bin/gem2rpm <mygemname-version>.gem > rubygem-<mygemname>.spec
After the .spec file is created next thing is to check if there are any hacks needed that needs to be preserved.
When the possible modifications are done it is time to add files, add new entry to .changes file and upload the new packaging.
...
