Closed rye closed 9 years ago
Can you try running git submodule init
in the directory and then running rake dist
again?
Submodule init happened automatically when he did rake dist
.
I can reproduce this in the case where Sprockets is installed as a gem. Trying to figure out why the gem version trumps the submodule that we explicitly put in the load path.
@savetheclocktower is correct; running git submodule init
in the Git root yields no output and no change in behavior.
Ah, it's because we're too clever; we don't try to install the submodule via git until after we require Sprockets. So if you've already got it installed, submodule init happens, but we see that require 'sprockets'
works, and we assume you don't need the submodule. This is dumb of us.
git submodule update
should fix it for now.
Indeed it does. Thanks for the help, closing this issue.
Reopening; working on a Rakefile
change that should handle this better. Thanks!
When I run
rake dist
, I get this output:Doing a bit of poking around, this appears to be because I have the latest version of Sprockets installed (2.12.3), and Sprockets::Secretary was retired entering the 2.x.x range. Should I install an outdated version of Sprockets, or could someone fix (or tell me what needs to be done to) the Rakefile?