For rake dist, grab the submodule for whatever selector engine was specified, even if it’s the default.

This is the thing I forgot to do when I removed our repo’s copy of Sizzle. That version of Sizzle _did_ get used if you tried to `rake dist` but you didn’t have the Sizzle submodule initialized. Considering that we’d have fetched the submodule automatically anyway, it’s not clear how much of a victory this was for user-friendliness.

Author: savetheclocktower

Rakefile

@@ -170,18 +170,12 @@ EOF
 
   def self.get_selector_engine(name)
     return if !name
-    # If the submodule exists, we should use it, even if we're using the
-    # default engine; the user might have fetched it manually, and thus would
-    # want to build a distributable with the most recent version of that
-    # engine.
+    # If the submodule exists, we should use it.
     submodule_path = File.join(ROOT_DIR, "vendor", name)
     return submodule_path if File.exist?(File.join(submodule_path, "repository", ".git"))
     return submodule_path if name === "legacy_selector"
 
-    # If it doesn't exist, we should fetch it, _unless_ it's the default
-    # engine. We've already got a known version of the default engine in our
-    # load path.
-    return if name == DEFAULT_SELECTOR_ENGINE
+    # If it doesn't exist, we should fetch it.
     get_submodule('the required selector engine', "#{name}/repository")
     unless File.exist?(submodule_path)
       puts "The selector engine you required isn't available at vendor/#{name}.\n\n"