Closed mlafeldt closed 10 years ago
Thanks for the report. The problem should be fixed by 91b09ea. Can you please test again if it works for you?
I can confirm that your change fixes the issue. Thanks!
As always, I'm looking forward to a new release. :)
@bernd Just noticed that your change also removes the ability to "fix" the gem path.
For example, we're doing something like this so that gems can be found under Debian:
# Make sure gem path matches target system so that system Ruby finds our gems.
ENV["GEM_HOME"] = "/var/lib/gems/1.8"
class HieraAwsGem < FPM::Cookery::RubyGemRecipe
name "hiera-aws"
version "0.5.0"
revision 0
maintainer "Mathias Lafeldt <mathias.lafeldt@jimdo.com>"
chain_package true
chain_recipes %w(aws-sdk json nokogiri uuidtools)
end
Is there a different way to do this now? I hope so; otherwise, we've got a problem.
Can you try with b9fb6c1 and the following recipe again?
class HieraAwsGem < FPM::Cookery::RubyGemRecipe
name "hiera-aws"
version "0.5.0"
revision 0
maintainer "Mathias Lafeldt <mathias.lafeldt@jimdo.com>"
# Make sure gem path matches target system so that system Ruby finds our gems.
environment['GEM_HOME'] = '/var/lib/gems/1.8'
chain_package true
chain_recipes %w(aws-sdk json nokogiri uuidtools)
end
Yes, that appears to work. Chained recipes also inherit the correct environment. Awesome!
Cool! Thanks for testing! :)
I'm going to cut a release soon.
Version 0.25.0 has been released to rubygems.
:shipit:
When installing
fpm-cookery
usingbundle install --path PATH
, Ruby packages build with that version will also be installed to PATH.e.g.
results in:
Any way I can fix this to still install to e.g.
/var/lib/gems/1.8
?PS: I'm installing gems to /tmp to work around a problem with bundler + sudo + git-based gems.