Difference between revisions of "Ruby Gem package guidelines"

From ArchWiki
Jump to: navigation, search
(Automation)
m (Notes: typo)
Line 12: Line 12:
  
 
== Notes ==
 
== Notes ==
Add {{Ic|--verbose}} to '''gem''' arguments to recive additional information in case of troubles.
+
Add {{Ic|--verbose}} to '''gem''' arguments to receive additional information in case of troubles.
  
 
{{Note|Usage of {{ic|--no-user-install}} '''gem''' argument is mandatory since latest Ruby versions (See {{Bug|28681}} for details).}}
 
{{Note|Usage of {{ic|--no-user-install}} '''gem''' argument is mandatory since latest Ruby versions (See {{Bug|28681}} for details).}}

Revision as of 07:32, 9 April 2013

Template:Package Guidelines

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 receive additional information in case of troubles.

Note: Usage of --no-user-install gem argument is mandatory since latest Ruby versions (See FS#28681 for details).

Example PKGBUILD

An example PKGBUILD can be found at /usr/share/pacman/PKGBUILD-rubygem.proto, which is in the abs package.

Automation

The gem installation can 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.

There are also multiple gem2arch tools which aid in automating the process of creating a ruby gem PKGBUILD. Make sure to manually check the PKGBUILD after generation. The original version is by Abhishek Dasgupta. Search for other versions of this tool in AUR (Search for gem2arch).