Skip to content

Idea: more flexible bundler config #6003

@hurricup

Description

@hurricup

As far as I get it, current bundler config (above project level) is shared between all rubies I might have.
But sometimes, some options are necessary only on particular version of ruby.

E.g. I encountered an issue installing nokogiri 1.6.6.4 on macOs for ruby 2.3 and 2.4. And this may be fixed with bundle config build.nokogiri --use-system-libraries

I'm not sure if it will harm other versions, where nokogiri installs fine without it, but I can easily imagine case when something like this happen.

So, it feels that some bundler options could depend on ruby version in use, and some, like build option, could be more precise, like include gem version constraints.

Or, another ruby-level config could be introduced to solve part of the issue. This feels like cheap solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions