Add Linux packaging tools to the build output and the buildbot archive.

Add Linux packaging tools to the build output and the buildbot archive.

This makes the buildbot archive hermetic for package building, rather than
pulling files from the package builder's source tree (e.g. BRANDING) and system
(e.g. lib32 stuff).

Note, this currently only applies to official builds since that's all we package.

This depends on:
http://codereview.chromium.org/115842
http://codereview.chromium.org/113966

[sgk, 2009-05-28 04:15:31]

lgtm, modulo one stylistic change

http://codereview.chromium.org/115843/diff/1/3
File chrome/installer/installer.gyp (right):

http://codereview.chromium.org/115843/diff/1/3#newcode82
Line 82: ['OS=="linux"', {
Move this block ahead of OS=="win"; I've been informally trying to maintain
alphabetical order in the condition blocks.

[Michael Moss, 2009-05-28 19:45:40]

I actually had to rearrange a lot more of installer.gyp after merging with
recent changes. I wrapped all the Win targets in a condition, otherwise they
cause errors on Linux due to unmet target dependencies (e.g. chrome_dll, which
doesn't exist for Linux).

[sgk, 2009-05-28 20:11:00]

cursory glance, most things look good, but i think you may be overwriting the
first conditions block so that the targets won't exist even on windows

http://codereview.chromium.org/115843/diff/15/1007
File chrome/installer/installer.gyp (right):

http://codereview.chromium.org/115843/diff/15/1007#newcode529
Line 529: 'conditions': [
It looks to me like this 'conditions' block is at the same level as the previous
'conditions' block, which means they're going to fight and only one will win.

[Michael Moss, 2009-05-28 20:39:02]

OK, I merged the conditions blocks. I had tried to do that before and got
errors, but I think there was something else wrong in the gyp file. It seems to
work fine now.

[sgk, 2009-05-28 20:51:02]

yeah, looks like it.  lgtm