Difference between revisions of "Ruby Gem package guidelines"

From ArchWiki
Jump to navigation Jump to search
(gem2arch version are cleaned)
Line 9: Line 9:
== Examples ==
== Examples ==
For examples, please see {{AUR|github-gem}} {{AUR|ruby-json_pure}} {{AUR|ruby-hpricot}}.
For examples, please see {{AUR|github-rethinkdb}} {{AUR|ruby-json_pure}} {{AUR|ruby-hpricot}}.
== Notes ==
== Notes ==

Revision as of 02:13, 10 December 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


For examples, please see github-rethinkdbAUR ruby-json_pureAUR ruby-hpricotAUR.


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).


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


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 is also gem2archAUR tools which aid in automating the process of creating a ruby gem PKGBUILD. Make sure to manually check the PKGBUILD after generation.