We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since libsass must be statically linked, it would be convenient if the release tarballs bundled the matching libsass version and used that by default.
The text was updated successfully, but these errors were encountered:
Do you mean the matching libsass source? On 20 Aug 2015 06:23, "David Thompson" [email protected] wrote:
Since libsass must be statically linked, it would be convenient if the release tarballs bundled the matching libsass version and used that by default. — Reply to this email directly or view it on GitHub #135.
— Reply to this email directly or view it on GitHub #135.
Sorry, something went wrong.
@xzyfer Yes, that is what I mean.
You're right, we should be less lazy about sassc.
No branches or pull requests
Since libsass must be statically linked, it would be convenient if the release tarballs bundled the matching libsass version and used that by default.
The text was updated successfully, but these errors were encountered: