Support for SASS_PATH

[craigbarnes]

Just making a note of this Sass 3.2 feature, not currently supported by libsass:

You can now set the SASS_PATH environment variable in your shell (a.k.a terminal) to a colon delimited list of directories and Sass will automatically look in each of them when finding a file for @import.
In ruby, the SASS_PATH environment variable will be loaded into the mutable property Sass.load_path where it can further manipulated if necessary. Sass.load_path defaults to an empty array.
-- http://chriseppstein.github.com/blog/2012/08/23/sass-3-2-is-released/

[HamptonMakes]

I'm not 100% sure this is something that should be in libsass. Seems more like SassC or a wrapper's job. We try and keep as much OS-specific stuff out of libsass as we can.

[chriseppstein]

Are there docs on what is required of wrappers using libsass in order to create a compliant implementation?

[lbastendorff]

Is this not what the sassc -I (import) option does, or am I missing something?

Usage: ../sassc [OPTION]... [FILE]

Options:
-o OUTFILE Write output to specified file.
-t NAME Output style. Can be: nested, compressed.
-l Emit comments showing original line numbers.
-g Emit source map.
-I PATH Set Sass import path.
-h Display this help message.

Or was this option added in response to this issue and therefore this issue should now be closed?

[craigbarnes]

We try and keep as much OS-specific stuff out of libsass as we can.

getenv is in C89.

Is this not what the sassc -I (import) option does, or am I missing something?

Yes, of course, but environment variables aren't the same thing as arguments. Some programs take command-line arguments, some take config files, some take API arguments but none of those things are visible to libsass without being passed explicitly. The environment is to available to all linked libraries and sub-processes automatically.

In a way, SASS_PATH is part of a public API, if people are already using it in Makefiles and build systems.

[lbastendorff]

Got it. Failed to realise we were talking about environment variables.

[HamptonMakes]

Yeah, this is something that the host wrapper should deal with. We want to work with environments without environment variables. Many host applications would certainly not want their embedded library referencing env variables with it being aware of it.

[craigbarnes]

We want to work with environments without environment variables.

getenv is C89. Very few environments exist without environment variables.

Many host applications would certainly not want their embedded library referencing env variables with it being aware of it.

Every process running on your system right now is referencing env variables. For example, libc uses LANG, LC_NUMERIC etc.

[HamptonMakes]

libsass is loosely modeled on libraries like libxml, which (afaik) don't use environment variables to change their behaviour. This is a very, very, very easy feature to add to sassc which would be the appropriate place to handle interactions with the operating system.

What adaptor are you using?

[chriseppstein]

Agree, this should be supported by the libsass frontends. We should have a
guide of things that frontends are required to do in order to be a
compliant frontend.

[xtianus79]

So what was the final outcome of this? I feel it is should be native to using sass sheets however that is achieved

[xzyfer]

@xtianus79 as stated above this does not belong in LibSass, but in the adaptors. For instance it has recently been added to node-sass.

[metaskills]

If you are using Ruby and either Ruby Sass or SassC with SassC-Rails, we have found this little gem useful and everything just works no matter which pre-processor we use.

[metaskills]

WHOOPS! Link here: https://github.com/customink/sass_paths