|(22 intermediate revisions by 15 users not shown)|
management (English)]] |+|
Category:Package development (English)]] |+|
|−|[[Category:Guidelines (English)]] | |
|−|[[Category:Development (English)]] | |
| || |
|−|==Package Naming== |+|
|−|For libraries, use "ruby-gemname". For applications, use the program name | |
| || |
For examples, please see [http://
aur. archlinux. org/packages. php?ID=24484 github-gem] [ http://aur.archlinux.org/packages.php? ID= 24483 ruby-json_pure] |+|
== Examples ==
For examples, please see
[http://.. . [://aur.archlinux.org/packages.php?=
Revision as of 13:16, 13 June 2012
Writing PKGBUILDs for software written in Ruby.
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-gemAUR ruby-json_pureAUR ruby-hpricotAUR.
--verbose to gem arguments to recive additional information in case of troubles.
An example PKGBUILD can be found at
/usr/share/pacman/PKGBUILD-rubygem.proto, which is in the abs package.
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