rubygems-bundler-uninstaller: command not found about rubygems-bundler HOT 17 CLOSED

how about ls -l /usr/bin/rubygems-bundler-uninstaller and which -a rubygems-bundler-uninstaller

from rubygems-bundler.

$ ls -l /usr/bin/rubygems-bundler-uninstaller
ls: /usr/bin/rubygems-bundler-uninstaller: No such file or directory

and

$ which -a rubygems-bundler-uninstaller
<nothing>

from rubygems-bundler.

aha! (sorry I did not noticed earlier - had sleepless night), you should use executable-hooks-uninstaller what issue do you have exactly with rubygems-bundler (except the uninstaller)?

from rubygems-bundler.

updated instructions, please let me know if you hit any issues with the gem(s)

from rubygems-bundler.

Ok, I will try executable-hooks-uninstaller.

In fact, rubygems-bundler does not prevent me to launch my commands without bundle exec:

$ cd my_project_with_local_gems/
$ bundle list
Gems included by the bundle:
  * bundler (1.5.2)
  * chunky_png (1.2.9)
  * compass (0.12.2)
  * fssm (0.2.10)
  * oily_png (1.1.0)
  * ruby_gntp (0.3.4)
  * sass (3.2.12)
  * sass-globbing (1.1.0)
$ compass version
-bash: compass: command not found
$ bundle exec compass version
Compass 0.12.2 (Alnilam)
Copyright (c) 2008-2014 Chris Eppstein
Released under the MIT License.
Compass is charityware.
Please make a tax deductable donation for a worthy cause: http://umdf.org/compass

That is why I tried to reinstall rubygems-bundler ^^

from rubygems-bundler.

can you show me ~/.bundle/config

from rubygems-bundler.

$ cat .bundle/config
---
BUNDLE_PATH: .vendors/bundler
BUNDLE_DISABLE_SHARED_GEMS: '1'

from rubygems-bundler.

this is bug but it can not be solved because bundler does not allow hooking into gem installation process when rubygems is disabled (BUNDLE_DISABLE_SHARED_GEMS: '1') ... usually I just advice to not use --deployment flag with bundle install, try instead:

rm .bundle/config
bundle install --path  .vendors/bundler

from rubygems-bundler.

I was well used --path flag to locally install my gems. I was already using it on my projects when I was on Moutain Lion (with BUNDLE_DISABLE_SHARED_GEMS: '1' in my local bundler configs).

Do you want that I open a new issue?

from rubygems-bundler.

when there is BUNDLE_DISABLE_SHARED_GEMS: '1' the only way it will work is that you also install the gems you want to use with gem install ... then the gem binaries are generated using executable-hooks and rubygems-bundler can do it's job by loading Bundler.setup, there is no solution for this problem now ... and it is possible there will be no solution for it, but on a bright side rubygems is already implementing most of bundler and it should be possible to drop bundler and rubygems-bundler and make rubygems load proper gem versions with one environment variable => https://coderwall.com/p/html5w (export RUBYGEMS_GEMDEPS=-)

from rubygems-bundler.

Indeed, on my old OSX I had the gems installed globally in older versions.
Thank you for the explanation and additional information on the future of RubyGems!

So, the simplest solution for me is to install Compass in the system scope. And it works:

$ cd
$ sudo gem install compass --no-document
9 gems installed

$ gem list

*** LOCAL GEMS ***

bundler (1.5.2)
bundler-unload (1.0.2)
CFPropertyList (2.2.0)
chunky_png (1.2.9)
compass (0.12.2)
executable-hooks (1.3.1)
ffi (1.9.3)
fssm (0.2.10)
libxml-ruby (2.6.0)
listen (1.1.6)
nokogiri (1.5.6)
rb-fsevent (0.9.4)
rb-inotify (0.9.3)
rb-kqueue (0.2.0)
rubygems-bundler (1.4.2)
rubygems-update (2.2.1)
sass (3.3.0.rc.2)
sqlite3 (1.3.7)

$ sass -v
Sass 3.3.0.rc.2 (Maptastic Maple)

$ cd my_project_with_local_gems/
$ sass -v
Sass 3.2.12 (Media Mark)

from rubygems-bundler.

exactly, you should have the same effect when using only --path instead of --deployment for bundle install

from rubygems-bundler.

Note: I never used --deployment with bundle install, I always used --path. But, this time, this was not working.

Thx for your time!

from rubygems-bundler.

oh wait, so if you do:

rm .bundle/config
bundle install --path  .vendors/bundler

then it also generates the following line in .bundle/config?

BUNDLE_DISABLE_SHARED_GEMS: '1'

from rubygems-bundler.

Absolutely.

from rubygems-bundler.

oh, then this is new, last time I was playing with --path this was not happening, I need to find out then how to fix it

from rubygems-bundler.

oh it appears I was wrong, bundle install --path was always disabling shared gems, (always = already in 1.0.22) ... it looks like you would have to abandon the --path or install the gem manually like you did.

from rubygems-bundler.