summaryrefslogtreecommitdiffstats
path: root/ash/wm/frame_painter.cc
diff options
context:
space:
mode:
authormarkus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-21 22:09:41 +0000
committermarkus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-21 22:09:41 +0000
commitb11411c46daf81c38c40b69da5be45c74ee4dd78 (patch)
tree3d91857d5743016b117dce587a8d517750761d03 /ash/wm/frame_painter.cc
parentd603ca97812db754aeaff4e672e374a8c71f210d (diff)
downloadchromium_src-b11411c46daf81c38c40b69da5be45c74ee4dd78.zip
chromium_src-b11411c46daf81c38c40b69da5be45c74ee4dd78.tar.gz
chromium_src-b11411c46daf81c38c40b69da5be45c74ee4dd78.tar.bz2
Fixed a few more minor nitpicks:
- "apt-cache show" is more appropriate for us then "dpkg --print-avail" - the test that was supposed to find the correct name for the nspr and nss libraries didn't work correctly for distributions (e.g. natty) that for a transition period included both versions of the library. The new test has been verified to work with natty. - it is annoying that the "--clean" option sometimes fails with a hard-to-understand error message. We now always use "sudo" to avoid confusing users. - apart from dbus, some distributions apparently also keep rsyslogd running after installing the build dependencies. If this keeps popping up as a problem, we might have to eventually device a more generic solution. - when the user told us to remove an old install, try to remove all traces, instead of just the parts that cost a lot of disk space. BUG=none TEST=verify that we can install natty32bit (with debug symbols) and that afterwards Chrome can be built. Review URL: https://chromiumcodereview.appspot.com/9764004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128068 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash/wm/frame_painter.cc')
0 files changed, 0 insertions, 0 deletions