search

diegoles / closure-library

Automatically exported from code.google.com/p/closure-library
0 stars 0 forks source link

Don't include path to depswriter.py, since it may vary, causing noise in source control. #411

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently depswriter.py generates a line like this in your deps file:

    // This file was autogenerated by ../../webapp/static/closure/library/closure/bin/build/depswriter.py.

Including the path to depswriter.py is undesirable.

Trivial fix which removes the path and uses __file__ instead of argv[0]: 
http://codereview.appspot.com/5533067

In my case, I have my deps file checked into source control, but people on the 
team regularly regenerate it as part of their daily workflow (there's a script 
that runs the code through closure compiler and depswriter).  Depending on 
where they regenerate from, the path to depswriter.py will vary, causing the 
file to appear changed in source control, even though nothing has actually 
changed.

Thanks!

Original issue reported on code.google.com by mikele...@gmail.com on 11 Jan 2012 at 6:57

GoogleCodeExporter commented 8 years ago 
assigning to self.  CLA has been signed so this can be ingested.

Original comment by nn...@google.com on 11 May 2012 at 7:49