summaryrefslogtreecommitdiff
path: root/dev-python/bitarray/bitarray-0.8.1.ebuild
diff options
context:
space:
mode:
authorHans de Graaff <graaff@gentoo.org>2015-12-21 21:08:13 +0100
committerHans de Graaff <graaff@gentoo.org>2015-12-30 09:10:07 +0100
commitd0d66933b9a8e7ad8bc3c75e03795f7db2399e71 (patch)
treef2e9e288206a559ee0a9b86a12e2c615d2a7d151 /dev-python/bitarray/bitarray-0.8.1.ebuild
parenta1b950cb1d47e3654e72ad6ba30ba7d09ad1e4f7 (diff)
downloadgentoo-d0d66933b9a8e7ad8bc3c75e03795f7db2399e71.tar.gz
gentoo-d0d66933b9a8e7ad8bc3c75e03795f7db2399e71.tar.bz2
gentoo-d0d66933b9a8e7ad8bc3c75e03795f7db2399e71.zip
eclass/ruby-fakegem.eclass: support non-default bindir
By default gems can provide binaries to be bin-wrapped in /usr/bin in a directory called "bin" in the gem. This is only a default, and it is possible for the gem to indicate that another directory contains the binaries to be bin-wrapped using the gemspec bindir option. dev-ruby/rspec-core and dev-ruby/bundler are gems where the binaries are placed in an "exe" directory. This change introduces RUBY_FAKEGEM_BINDIR, defaulting to "bin" for backward compatibility, allowing this directory to be specified.
Diffstat (limited to 'dev-python/bitarray/bitarray-0.8.1.ebuild')
0 files changed, 0 insertions, 0 deletions