Proof of concept for automatic, bundler-managed gemsets #53

Closed
daytonn opened this Issue Dec 19, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@daytonn

daytonn commented Dec 19, 2012

Using the same basic function as chruby_auto I created gemsets based on the Gemfile's parent directory name and replace the entire GEM environment variables with that single gem location.

Logically assuming all Gemfiles have a corresponding gemset means shim-less, bundler-managed gems.

https://github.com/daytonn/chruby/blob/automatic-gemsets/scripts/gemsets.sh

This needs tests and could be refactored into a shared function that chruby_auto could also use.

This is a proof of concept.

Thoughts?

@postmodern

This comment has been minimized.

Show comment
Hide comment
@postmodern

postmodern Dec 19, 2012

Owner

You might want to look at chgems. It sets GEM_HOME to $PWD/.gem/$ruby/$version to make cleanup easy and spawns a sub-shell instead of auto-switching. Also, I don't think it's wise to use gemsets for every bundler project.

Owner

postmodern commented Dec 19, 2012

You might want to look at chgems. It sets GEM_HOME to $PWD/.gem/$ruby/$version to make cleanup easy and spawns a sub-shell instead of auto-switching. Also, I don't think it's wise to use gemsets for every bundler project.

@daytonn

This comment has been minimized.

Show comment
Hide comment
@daytonn

daytonn Jan 4, 2013

Scratched my own itch. For others with this itch: https://github.com/daytonn/auto-gemsets

daytonn commented Jan 4, 2013

Scratched my own itch. For others with this itch: https://github.com/daytonn/auto-gemsets

@postmodern

This comment has been minimized.

Show comment
Hide comment
@postmodern

postmodern Jun 16, 2013

Owner

Closing now that auto-gemsets is available to users.

Owner

postmodern commented Jun 16, 2013

Closing now that auto-gemsets is available to users.

@postmodern postmodern closed this Jun 16, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment