diff options
| author |   Hans de Graaff <graaff@gentoo.org> | 2021-01-03 07:58:51 +0100 |
|---|---|---|
| committer | Hans de Graaff <graaff@gentoo.org> | 2021-02-07 07:28:43 +0100 |
| commit | ca7284468286d72f5bf9e2349a0661584bbc59c4 (patch) | |
| tree | 36c0a6c0b928cb134b36008b09d63d9aa61795f4 /sec-policy | |
| parent | www-servers/puma: add 5.2.1 (diff) | |
| download | gentoo-ca7284468286d72f5bf9e2349a0661584bbc59c4.tar.gz gentoo-ca7284468286d72f5bf9e2349a0661584bbc59c4.tar.bz2 gentoo-ca7284468286d72f5bf9e2349a0661584bbc59c4.zip | |
ruby-fakegem.eclass: support for extensions
Up to now handling of extensions was done in each ebuild that
contained them. This means that handling is often
inconsistent (e.g. not taking multilib's get_modname into account) and
there is a lot of duplicated code in ebuilds.
Furthermore, this also does not install extensions into the special
extensions directory. rubygems itself has been doing this for some
time, and now bundler 2.2.x has started to explicitly check for the
extensions in this directory, making it incompatibly with our previous
way of installing gems.
The new RUBY_FAKEGEM_EXTENSIONS array and
RUBY_FAKEGEM_EXTENSION_LIBDIR options provide support for installing
extensions automatically based on these settings, taking into account
that the extensions also must be part of testing and that it must be
installed properly.
Signed-off-by: Hans de Graaff <graaff@gentoo.org>
Diffstat (limited to 'sec-policy')
0 files changed, 0 insertions, 0 deletions