Ruby Gem package guidelines
32-bit – CLR – Cross – Eclipse – Electron – Font – Free Pascal – GNOME – Go – Haskell – Java – KDE – Kernel – Lisp – MinGW – Node.js – Nonfree – OCaml – Perl – PHP – Python – R – Ruby – Rust – VCS – Web – Wine
For libraries, use
ruby-$gemname. For applications, use the program name. In either case, the name should be entirely lowercase.
ruby- prefix even if
$gemname already starts with word
ruby. It is needed to avoid future name clashes in case if a gem with shorter name appear. It also makes names more easily parsable by tools (think about PKGBUILD generators/version or dependency checkers, etc...).
If you need to add a versioned package then use
ruby-builder-3.2.1. So rubygem dependency
builder=3.2.1 will turn into
ruby-builder-3.2.1 Arch package.
In case if you need to resolve "approximately greater" dependency
~> then package should use version without the last part, e.g. rubygem dependency
builder~>3.2.1 will turn into
ruby-builder-3.2. An exception for this rule is when "approximately greater" dependency matches the latest version of the gem - in this case avoid introducing a new versioned package and use just
ruby-$gemname instead (the HEAD version).
Another problem with versioned packages is that it can conflict with other versions, e.g. because the packages install the same files in
/usr/bin. One solution for this problem is that versioned packages should not install such files - only HEAD version package can do this.
For examples, please seeAUR or .
--verbose to gem arguments to receive additional information in case of troubles.
--no-user-installgem argument is mandatory since latest Ruby versions (See FS#28681 for details).
As an alternative to manually managing gemfiles, you might also want to consider quarry, a non-official repository of pre-built binary arch packages. See Quarry for details.
Package contains reference to $pkgdir
Sometimes when you build the package you can see following warning
WARNING: Package contains reference to $pkgdir. Some packed files contain absolute path of directory where you built the package. To find these files run
cd pkg && grep -R "$(pwd)". Most likely the reason will be hardcoded path in
extcontains native extension code usually written in C. During the package installation rubygems generates a Makefile using
makeis called, it compiles a shared library and copies one to
gem install is over the
Makefile is not needed anymore. In fact none of the files in
ext is needed and it can be completely removed by adding
rm -rf "$pkgdir/$_gemdir/gems/$_gemname-$pkgver/ext" to