sass / ruby-libsass Goto Github PK

Copyright may not be assigned to other ppl by German law, only exploitation/usage right. Just saying. :D

I think this is also true for other European countries.

This is also the reason you can't release anything as public domain in Germany.

Feel free to close this issue again.

Are there any plans to make an FFI version of this for people who cannot / will not use C Extension ruby gems?

Using

#Gemfile snippet
gem 'sassc', :git => 'git://github.com/hcatlin/sassruby.git'

and doing bundle install results in the following

Using sassc (0.1) from git://github.com/hcatlin/sassruby.git (at master)
sassc at /Users/chaos/.rvm/gems/ruby-2.0.0-p353@sinatra-base/bundler/gems/sassruby-bf5d8cf236b1 did not have a valid gemspec.
This prevents bundler from installing bins or native extensions, but that may not affect its functionality.
If you need to use this package without installing it from a gem repository, please contact ["[email protected]"] and ask them to modify their .gemspec so it can work with gem build.
The validation message from Rubygems was:
["ext/libsass/extconf.rb"] are not files

I can't get it working in my (non-Rails) project, it complains about the same issues as someone talked about on Stack Overflow:

https://stackoverflow.com/questions/26688631/using-libsass-with-rails-asset-pipeline

So I'm going to try to fix the problem by going step by step in this gem and getting help along each step of the way. My first obvious port of call is to clone the github sources, bundle install and ensure the automated tests run.

$ ruby -v
ruby 1.9.3p429 (2013-05-15 revision 40747) [x86_64-darwin14.0.0]
$ bundle             
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies...
Using rake 10.3.2
Using hitimes 1.2.2
Using timers 4.0.1
Using celluloid 0.16.0
Using coderay 1.1.0
Using ffi 1.9.3
Using formatador 0.2.5
Using rb-fsevent 0.9.4
Using rb-inotify 0.9.5
Using listen 2.7.9
Using lumberjack 1.0.9
Using method_source 0.8.2
Using slop 3.6.0
Using pry 0.10.1
Using thor 0.19.1
Using guard 2.6.1
Using test-unit 2.5.5
Using guard-test 2.0.5
Installing rake-compiler 0.9.3
Using sassc 0.3 from source at .
Using bundler 1.7.7
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
$ bundle exec rake test
$ bundle exec rake spec
$ 

So no tests of any description ran (or they all ran, but output nothing) and neither rake command gave an error. I'm assuming that no tests ran because doing this also outputs nothing:

$ bundle exec rake spec SPEC_OPTS="--format documentation"
$ 

So, can anyone else get the tests to run, if so, what am I missing?

Next step after this one is to try to create a simple test case that uses the gem and report problems with it...

So I'm curious, I was wondering wether this was possible to integrate into rails but there seems to be a missing file called libsass.bundle, which seems to be a OSX extension. I'm wondering wether this dependency is planned or should I see about working around this?

This gem seems great, but I'm wondering why not publish it on RubyGems?