Difference between revisions of "Ruby Gem package guidelines"
(recycle prev. summary as intro) |
Kynikos.bot (talk | contribs) (Template:i18n is deprecated, use interlanguage links, see Help talk:I18n#"Dummy" interlanguage links and deprecation of Template:i18n) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:Package development | + | [[Category:Package development]] |
| − | + | [[it:Ruby Gem Package Guidelines]] | |
{{Package Guidelines}} | {{Package Guidelines}} | ||
| − | Writing [[PKGBUILD]]s for | + | Writing [[PKGBUILD]]s for software written in [[Ruby]]. |
== Package Naming == | == Package Naming == | ||
Revision as of 13:16, 13 June 2012
Writing PKGBUILDs for software written in Ruby.
Package Naming
For libraries, use ruby-gemname. For applications, use the program name. In either case, the name should be entirely lowercase
Examples
For examples, please see github-gemAUR ruby-json_pureAUR ruby-hpricotAUR.
Notes
Add --verbose to gem arguments to recive additional information in case of troubles.
Example PKGBUILD
An example PKGBUILD can be found at /usr/share/pacman/PKGBUILD-rubygem.proto, which is in the abs package.
Automation
Abhishek Dasgupta wrote gem2arch to aid in automating the process of creating a ruby gem PKGBUILD. Make sure to manually check the PKGBUILD after generation. There are multiple versions of this tool in AUR (Search for gem2arch).
The gem installation can also be automated completely with the tool pacgemAUR which creates a temporary PKGBUILD, calls makepkg and namcap. The resulting package is then installed with sudo pacman.