Bben@chromium.orgRemove more set noparents
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Remove the rest of #pragma once in one big CL. For context see this thread: https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/RMcVNGjB4II TBR=thakis,pkasting,jam git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146163 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Remove more set noparents BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/10824025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148406 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Finish the job that r48732 started. Move the remainder of the installer-related files from chrome/tools/build/mac to chrome/installer/mac. BUG=45017 TEST=none Review URL: http://codereview.chromium.org/2755007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49551 0039d316-1c4b-4281-b951-d872f2087c98 | 15 年前 | |
[Mac] packaging process cleanup: Net of this is the zip off the official builder will have everything for packaging so the final signing/dmg creation is self contained instead of having to live in both places. - Move all the installer related bits into the installer folder - Add the collection of these bits into a specific target - Collect the internal bits also during the installer target BUG=42635 TEST=none Review URL: http://codereview.chromium.org/2417007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@48732 0039d316-1c4b-4281-b951-d872f2087c98 | 15 年前 | |
A less wordy version of r85947 and r85948. BUG=83180 TEST=none Review URL: http://codereview.chromium.org/7049027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@86039 0039d316-1c4b-4281-b951-d872f2087c98 | 14 年前 | |
Typo police. BUG=none TEST=none Review URL: http://codereview.chromium.org/6802015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80671 0039d316-1c4b-4281-b951-d872f2087c98 | 15 年前 | |
Do Keychain reauthorization at update time. In addition to the at-launch reauthorization, this adds an at-update reauthorization step. It only runs for users not on a system Keystone ticket, because the updater runs as root when on a system ticket, and root can't read individual user's Keychains. The at-update reauthorization is intended to handle the reauthorization for users who rarely restart Chrome and might miss out on the at-launch step during the window where Chrome is signed by the old certificate but has the new reauthorization code in place. The at-update reauthorization step can remain in place even after the certificate switch occurs by shipping an old reauthorization stub binary signed with the old certificate. BUG=108238 TEST=none Review URL: https://chromiumcodereview.appspot.com/10377173 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137501 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Use lsregister -f to work around Launch Services problems. BUG=135249 Review URL: https://chromiumcodereview.appspot.com/10816025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147943 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Finish the job that r48732 started. Move the remainder of the installer-related files from chrome/tools/build/mac to chrome/installer/mac. BUG=45017 TEST=none Review URL: http://codereview.chromium.org/2755007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49551 0039d316-1c4b-4281-b951-d872f2087c98 | 15 年前 | |
Split sign.sh into two pieces to allow the contents of the versioned directory to be signed independently of the outer browser application bundle. BUG=45017 TEST=none Review URL: http://codereview.chromium.org/2749014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49552 0039d316-1c4b-4281-b951-d872f2087c98 | 15 年前 | |
Do Keychain reauthorization at update time. In addition to the at-launch reauthorization, this adds an at-update reauthorization step. It only runs for users not on a system Keystone ticket, because the updater runs as root when on a system ticket, and root can't read individual user's Keychains. The at-update reauthorization is intended to handle the reauthorization for users who rarely restart Chrome and might miss out on the at-launch step during the window where Chrome is signed by the old certificate but has the new reauthorization code in place. The at-update reauthorization step can remain in place even after the certificate switch occurs by shipping an old reauthorization stub binary signed with the old certificate. BUG=108238 TEST=none Review URL: https://chromiumcodereview.appspot.com/10377173 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@137501 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Sign Chrome with the new Apple Developer ID certificate. This removes the at-launch reauthorization step, but retains the at-update reauthorization step for user Keystone tickets. The at-update helper stubs are now prebuilt binaries signed with the old certificate, so the old target for the stubs is removed and replaced with a straight file copy. The new designated requirement only allows access to Keychain items for Chrome official builds (canary and non-Canary) signed by the new Developer ID certificate. BUG=116210 TEST=none Review URL: https://chromiumcodereview.appspot.com/10534027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140817 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Supply an explicit designated requirement for all internal components during signing. The implied designated requirement produced when signing on Lion cannot be satisfied on pre-Lion systems. This was already addressed by providing an explicit designated requirement for the outer .app bundle. This change also provides an explicit designated requirement for inner components. The Parental Controls feature apparently requires an application to meet its designated requirement. Since the requirement for inner components such as the helper would never be met on 10.6 (or presumably 10.5), it was impossible to launch such inner components. This prevented any renderer processes from ever starting up. The user would only see sad tabs and endless OS prompts, and the browser would effectively be useless. BUG=131682, 134311 TEST=Turn on Parental Controls and set it to limit applications. Launch Chrome. After a possible initial prompt asking whether Chrome should be permitted (authenticate and say yes), Chrome should function normally. There should be no prompts about Chrome Helper, Chrome Helper EH, or Chrome Helper NP. Web pages should load normally. There should be no sad tabs. Note that there may still be a prompt about ksadmin. Review URL: https://chromiumcodereview.appspot.com/10696101 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145370 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 |