Sha256: 8d1c812667520e1599f8f0faea74ab61d00c58aed19e6c5dfde941df63d33ecd
Contents?: true
Size: 1.26 KB
Versions: 5
Compression:
Stored size: 1.26 KB
Contents
# -*- encoding: utf-8 -*-
$:.push File.expand_path("../lib", __FILE__)
require "sprockets/sass/version"
Gem::Specification.new do |s|
s.name = "sprockets-sass"
s.version = Sprockets::Sass::VERSION
s.authors = ["Pete Browne"]
s.email = ["me@petebrowne.com"]
s.homepage = "http://github.com/petebrowne/sprockets-sass"
s.summary = %q{Better Sass integration with Sprockets 2.0}
s.description = %q{When using Sprockets 2.0 with Sass you will eventually run into a pretty big issue. `//= require` directives will not allow Sass mixins, variables, etc. to be shared between files. So you'll try to use `@import`, and that'll also blow up in your face. `sprockets-sass` fixes all of this by creating a Sass::Importer that is Sprockets aware.}
s.rubyforge_project = "sprockets-sass"
s.files = `git ls-files`.split("\n")
s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
s.require_paths = ["lib"]
s.add_dependency "sprockets", "~> 2.0"
s.add_development_dependency "rake"
s.add_development_dependency "rspec", "~> 2.6"
s.add_development_dependency "test-construct", "~> 1.2"
s.add_development_dependency "sass", "~> 3.1"
end
Version data entries
5 entries across 5 versions & 1 rubygems