Comment #2 on issue 23315 by [email protected]: archive_build should be driven from the source http://code.google.com/p/chromium/issues/detail?id=23315
This isn't the only script that has issues like this. My thoughts would be: The information about: - what symbols to upload - what bits to save - what to put in the archive Should all go into the src tree to it can track the changes to the core tree. The formation about: - where to archive symbols - where to save the archive and other bits Should all live in the build scripts since it shouldn't be dependent on the actual version being built. Having said that, one of the weaknesses of these scripts is some of they have a list of files within the tree, but then they apply a filter to exclude stuff, those aren't in the tree. We really need to get both lists in the tree. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
