无法激活 susy-2.1.1，因为 sass-3.2.17 与 sass 冲突(~>3.3.0) [英] Unable to activate susy-2.1.1, because sass-3.2.17 conflicts with sass (~> 3.3.0)

问题描述

我已经安装了最新版本的 compass、sass 和 susy.但我仍然收到此错误:

I have installed the latest versions of compass, sass and susy. But still I am getting this error:

Unable to activate susy-2.1.1, because sass-3.2.17 conflicts with sass (~> 3.3.0)

有人知道这个 Ruby 是怎么工作的吗?

Anyone knows how this Ruby thing works?

这是我安装的 gem 的列表:

This is the list of my installed gems:

*** LOCAL GEMS ***

CFPropertyList (2.2.0)
chunky_png (1.3.0)
compass (0.12.4)
compass-core (1.0.0.alpha.19)
compass-import-once (1.0.4)
compass-rails (1.1.3)
fssm (0.2.10)
libxml-ruby (2.6.0)
multi_json (1.9.2)
nokogiri (1.5.6)
rb-fsevent (0.9.4)
rubygems-update (2.2.2)
sass (3.3.4, 3.3.3, 3.2.17)
sqlite3 (1.3.7)
susy (2.1.1)

推荐答案

如果你使用Bundler，它将确保你的Gemfile中的gem是你项目使用的.因此，您的 Gemfile 应指定susy"、~>2.1.1"和sass"、~>3.3.2"，以及您需要的任何其他内容，例如breakpoint"、~>2.4.1".然后，在您的 Ruby gems 文件夹中安装什么版本就无关紧要了.然后，当您执行捆绑安装"时，Bundler 会确保您的项目仅使用正确的依赖项.这当然是通过终端的 CLI 指令.或者，如果您不想使用 Bundler，只需执行sudo gem uninstall sass -v 3.2.17"即可.

If you use Bundler, it will ensure that the gems in your Gemfile are the ones used by your project. So your Gemfile should specify "susy", "~>2.1.1" and "sass", "~>3.3.2", plus any other that you require, such as "breakpoint", "~>2.4.1". It then won't matter what versions are installed inside your Ruby gems folder. When you then do a 'bundle install', Bundler ensures that your project will only use the correct dependencies. This is, of course, a CLI instruction through the terminal. Alternatively, simply do a 'sudo gem uninstall sass -v 3.2.17', if you don't want to use Bundler.

这篇关于无法激活 susy-2.1.1，因为 sass-3.2.17 与 sass 冲突(~>3.3.0)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！