Bring back initPolymer, allow boot.js only if using "polymer_experimental.html".

pkg/pkg.gyp

 # Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 # for details. All rights reserved. Use of this source code is governed by a
 # BSD-style license that can be found in the LICENSE file.
 
 {
   'targets': [
     {
       'target_name': 'pkg_packages',
       'type': 'none',
       'actions': [
         {
           'action_name': 'make_pkg_packages',
           'inputs': [
             '../tools/make_links.py',
             '<!@(["python", "../tools/list_pkg_directories.py", "."])',
             '<!@(["python", "../tools/list_pkg_directories.py", '
                 '"third_party"])',
             '<!@(["python", "../tools/list_pkg_directories.py", '
                 '"../third_party/pkg"])',
             '<!@(["python", "../tools/list_pkg_directories.py", '
-                '"polymer/example/"])',
+                '"polymer/e2e_test/"])',

[Siggi Cherem (dart-lang), 2014/05/22 21:10:41]

we were mixing tests and examples together. I moved the tests to "e2e_test" in
the process of cleaning up here.

[Jennifer Messerly, 2014/05/23 07:20:06]

much better :)

out of curiosity could it be under test/e2e?

[Siggi Cherem (dart-lang), 2014/05/23 17:56:33]

I think yes. I'm happy to change it, but I'm slighly inclined to keep it as it
is. Like 'examples/', 'test/' will have a packages folder, but 'e2e_test' will
not. By naming it e2e_test we could more easily run these tests by actually
calling pub-get on the e2e test and not be worried about packages symlinks that
may be created from the pubspec in polymer.

           ],
           'outputs': [
             '<(SHARED_INTERMEDIATE_DIR)/packages.stamp',
           ],
           'action': [
             'python', '../tools/make_links.py',
             '--timestamp_file=<(SHARED_INTERMEDIATE_DIR)/packages.stamp',
             '<(PRODUCT_DIR)/packages',
             '<@(_inputs)',
           ],
         },
       ],
     },
   ],
 }