1 |
Hi, |
2 |
|
3 |
The current ruby eclasses work fairly well for ruby-only packages, but |
4 |
support for packages where ruby is only part of the package are not well |
5 |
served. As a start the ruby team proposes the following new eclass, |
6 |
ruby-single.eclass. The purpose of this eclass is to provide support for |
7 |
the case where a working ruby version needs to be accessed |
8 |
via /usr/bin/ruby. Examples of such packages are net-libs/webkit-gtk and |
9 |
sys-block/thin-provisioning-tools. |
10 |
|
11 |
The eclass is loosely modeled after the python-single eclass-r1, |
12 |
although not all the functionality available there can be or has been |
13 |
provided for ruby at the moment. We've tried to keep variable and method |
14 |
names compatible, though. |
15 |
|
16 |
Also contained in this email is a new ruby-utils eclass which contains |
17 |
code factored out of the current ruby-ng eclass, so that it can used by |
18 |
both eclasses. ruby-utils.eclass is not meant to be used in ebuilds. |
19 |
|
20 |
Full example code including an ebuild (app-admin/pwstore) is available |
21 |
in the "ruby" repository. |
22 |
|
23 |
Thanks, |
24 |
|
25 |
Hans |