Ruby Gem package guidelines

From ArchWiki
Revision as of 22:06, 19 March 2012 by Kynikos (Talk | contribs) (recycle prev. summary as intro)

Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Package Guidelines

Writing PKGBUILDs for sowtware 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.

Warning: 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

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.