Copy pyauto scripts and support libs to autotest image.

Copy pyauto scripts and support libs to autotest image.

This includes all the scripts and support libs needed to run PyAuto.

BUG=
TEST=

[zel, 2010-09-10 16:00:30]

Please note that you will have to make identical change in private overlays as
well. Don't check in this one unless you have private overlay CL ready.

http://codereview.chromium.org/3327014/diff/2001/3001
File chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild (right):

http://codereview.chromium.org/3327014/diff/2001/3001#newcode353
chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild:353:
"${CHROME_ROOT}"/src/chrome/test/pyautolib "${TEST_DIR}"/chrome/test/
why don't you copy this in .../pyautolib dir or somewhere inside .../out/Release
(where other binaries are).

[Nirnimesh, 2010-09-17 01:33:40]

Thanks for reviewing.
Apologies for responding back late (I think I've finally begun to understand the
chromeos build system now :)

Sent you another CL for corresponding changes to private overlay.

http://codereview.chromium.org/3327014/diff/2001/3001
File chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild (right):

http://codereview.chromium.org/3327014/diff/2001/3001#newcode353
chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild:353:
"${CHROME_ROOT}"/src/chrome/test/pyautolib "${TEST_DIR}"/chrome/test/
On 2010/09/10 16:00:30, zel wrote:
> why don't you copy this in .../pyautolib dir or somewhere inside
.../out/Release
> (where other binaries are).

Copying everything to out/Release would clutter it with all kinds of python
scripts, also there are some files with the same name in pyautolib and
functional dir. So I thought I'd try to preserve the dir structure. Besides,
this way the scripts know where to look for the data dir.

[zel, 2010-09-17 01:52:27]

LGTM

[zbehan, 2010-09-17 02:05:39]

Driveby: if you look at the most recent version of the ebuild (which
probably conflicted lots with you) by davidjames, it's no longer using
rsync, rather a wrapper function that we try to optimize for speed.

You'll have to rebase against that, can you change your commands to also not
be rsyncs?

On Thu, Sep 16, 2010 at 6:52 PM, <zelidrag@chromium.org> wrote:

> LGTM
>
>
> http://codereview.chromium.org/3327014/show
>

[Nirnimesh, 2010-09-17 02:33:46]

zehan, I'm already not using rsync. See my patchset 3.

Thanks for pointing though, I'll be on the lookout and merge as needed.

[zbehan, 2010-09-17 02:52:39]

Cool, I didn't notice that.

I was just making sure you don't miss the latest trends in
chromeebuildology. ;)

On Thu, Sep 16, 2010 at 7:33 PM, <nirnimesh@chromium.org> wrote:

> zehan, I'm already not using rsync. See my patchset 3.
>
> Thanks for pointing though, I'll be on the lookout and merge as needed.
>
>
> http://codereview.chromium.org/3327014/show
>

[zelidrag1, 2010-09-17 18:54:49]

LGTM