Remove LASTCHANGE dependency

remoting/remoting_host_win.gypi

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 {
   'variables': {
     'remoting_host_installer_win_roots': [
       'host/installer/win/',
     ],
     'remoting_host_installer_win_files': [
@@ skipping 371 matching lines @@
           ],
           'rules': [
             {
               'rule_name': 'version',
               'extension': 'jinja2',
               'variables': {
                 'lastchange_path': '<(DEPTH)/build/util/LASTCHANGE',
               },
               'inputs': [
                 '<(chrome_version_path)',
-                '<(lastchange_path)',

[Jamie, 2014/01/29 23:43:26]

Can you add a comment explaining why we don't want a dependency on lastchange?
Otherwise I can envision some well-meaning person adding this back in, thinking
it was an oversight.

[Sergey Ulanov, 2014/01/29 23:50:22]

Done.

                 '<(remoting_version_path)',
                 '<(RULE_INPUT_PATH)',
               ],
               'outputs': [
                 '<(SHARED_INTERMEDIATE_DIR)/remoting/<(RULE_INPUT_ROOT)',
               ],
               'action': [
                 'python', '<(remoting_localize_path)',
                 '--variables', '<(chrome_version_path)',
                 # |remoting_version_path| must be after |chrome_version_path|
@@ skipping 136 matching lines @@
                 '--defs', '<@(_defs)',
               ],
             },
           ],  # actions
         }, # end of target 'remoting_me2me_host_archive'
       ],  # end of 'targets'
     }],  # '<(wix_path) != ""'
 
   ],  # end of 'conditions'
 }