sassc-ruby can't be used with older Ruby, such as from older Linux distros' package repositories

[DeeDeeG]

Hi,

I'm reporting this issue on behalf of some bootstrap-sass users, which is a gem that depends on sassc-ruby. (See this issue here: twbs/bootstrap-sass#1182)

These users have trouble installing sassc-ruby due to its dependency on at least Ruby 2.3.3.

---

In general, some users currently depend on Ruby from distro package repositories. This is especially true of automatically managed environments, like Ansible configs, Docker images, Vagrant boxes etc. These users may be stuck on an older operating system version for one reason or another.

Debian before stretch and Ubuntu before Bionic, for instance, have Ruby older than 2.3.3 in their repositories. CentOS 7 also has an older ruby version in its repos. Specifically, these are the versions available last I checked:

• Ubuntu Trusty: 1.9.3
• CentOS 7: 2.0.0
• Debian Jessie: 2.1.5
• Ubuntu Xenial: 2.3.1

So with the latest Ruby from the distribution's package repos, these users can't install SassC-ruby.

---

For these users, perhaps this gem can be tested with older Ruby, and the gemspec file can be updated to allow older Ruby, such as can be found in the distributions' package repos?

[DeeDeeG]

Hi again folks, here's an update:

I tried running Travis CI on every minor release of Ruby back to 1.9.x. The result was that the Travis CI build failed for 1.9.3 (Travis CI link), but succeeded for 2.0.0, 2.1.9, 2.2.10, as well as the usual 2.3.7+.

Here's a link to my passing Travis CI results: https://travis-ci.com/DeeDeeG/sassc-ruby/builds/100168686

(Test is based on this branch: https://github.com/DeeDeeG/sassc-ruby/tree/Ruby-2.0.0 (@19f07df))

---

If you'd be okay with this as a pull request, let me know. I didn't want to blast your CI with a queue of 6 builds at once though, so I'm probably not going to submit it as a PR unless I hear back from someone here.

I'm definitely open to any feedback or changes you'd like me to make, either here or in a PR. And I personally think it'd make sense to test this a bit beyond just CI before merging.

Thanks! Sincerely,

- DeeDeeG

[dracmaAgil]

Hi, I have the same issue, I'm using linux mint and ruby 2.3.1 and there is no a ruby 2.3.3 version listed, the latest stable version is 2.3.1, 2.4.0 is not stable yet, what can I do to avoid this problem?

[dracmaAgil]

Hi, I have the same issue, I'm using linux mint and ruby 2.3.1 and there is no a ruby 2.3.3 version listed, the latest stable version is 2.3.1, 2.4.0 is not stable yet, what can I do to avoid this problem?

Hi again, I solve this updating ruby-build (I'm usign rbenv) with this command "cd /home/"your user"/.rbenv/plugins/ruby-build && git pull && cd -", after uodate, I list ruby vrsion ad there are from 2.3.2 to 2.3.8. I hoe this could help you guys!