Is there any way to declare a compilation dependency but NOT include it in the output? about less-rails

[metaskills]

This sounds like a sprockets question.
https://github.com/sstephenson/sprockets#the-depend_on-directive

[mikesnare]

Except that I've tried that and the file I used it in fails to compile due to variables not resolving (sorry for not pointing that out in my original post). I don't think the less-rails gem is set up to be able to depend on a file for purposes of compilation without that file being @import-ed into the source file.

Am I incorrect? If not, this seems like a reasonable potential addition to the gem, no?

[metaskills]

I am open to any reasonable potential addition. In fact, please open a pull request that at the minimal exposes the case that you are trying to resolve. I think it is too easy to get confused on all these import expectations without a failing expected use case. Case in point, I did that (see diff gist link) when talking around this issue. #28 (comment)

[mikesnare]

Ok, it seems odd to me to issue a pull request without supplying any code so here's the gist that should describe pretty clearly what it is I'm hoping to achieve.

I wouldn't even know where to start as far as the code goes. I'm not averse to helping out with this, I just don't know enough about how this works to even start.

[metaskills]

Ok, it seems odd to me to issue a pull request without supplying any code

Even if the code is a failing test case, it is still code. That is what I was talking about.