Move libvpx_new to libvpx

Move libvpx_new to libvpx

The move to libvpx_new happened before M47 (landed in 2524, M47 branch was 2526):
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable so is unlikely that a client would check out the old code at all, much less try to transition directly between the two versions.

Leave a compatibility layer for targets which need to be updated out of band (webrtc, libyuv)

Committed: https://crrev.com/8cdf034791388299f18fba186f2941313320b706
Cr-Commit-Position: refs/heads/master@{#378739}

[Johann, 2016-02-25 02:38:39]

Description was changed from

==========
Move libvpx_new back to libvpx

Leave a compatibility layer in case other targets need to be updated
==========

to

==========
Move libvpx_new back to libvpx

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

[Johann, 2016-02-25 02:50:03]

Description was changed from

==========
Move libvpx_new back to libvpx

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

to

==========
Move libvpx_new to libvpx

The move to libvpx_new happened in M47:
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable it is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

[Johann, 2016-03-01 14:51:51]

Description was changed from

==========
Move libvpx_new to libvpx

The move to libvpx_new happened in M47:
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable it is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

to

==========
Move libvpx_new to libvpx

The move to libvpx_new happened before M47 (landed in 2524, M47 branch was
2526):
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable so is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

[Johann, 2016-03-01 14:51:52]

johannkoenig@google.com changed reviewers:
+ brettw@chromium.org, kjellander@chromium.org, phajdan.jr@chromium.org,
tomfinegan@chromium.org

[Johann, 2016-03-01 15:44:30]

Hi, it seems enough time has passed to move libvpx_new back to libvpx. The
previous move landed before the M47 cut, so two full stable cycles with the old
code totally removed.

The purple failures appear to be unrelated trybot issues to me, but I waited
until after the M50 cut just in case.

This uses the last revision of the pass-through code to keep the libvpx_new
target until webrtc and libyuv can be updated. Other than that it's a fairly
straightforward move. If I recall correctly, between brettw@ and phajdan.jr@,
all the necessary approvals are covered.

This will be followed up with changes to webrtc and libyuv and ultimately the
deletion of libvpx_new.

[Johann, 2016-03-01 15:55:05]

If you're looking for places to review carefully, the files left behind in
libvpx_new are probably the most interesting:

https://codereview.chromium.org/1734613003/diff/30001/third_party/libvpx_new/...
https://chromium.googlesource.com/chromium/deps/libvpx/+/master/BUILD.gn

https://codereview.chromium.org/1734613003/diff/30001/third_party/libvpx_new/...
https://chromium.googlesource.com/chromium/deps/libvpx/+/master/libvpx.gyp

The LICENSE file was copied from libvpx because of the change to README.chromium
(both required by presubmit checks) but it will be deleted ~shortly when the
directory goes away. For some reason it doesn't show as new, but rather modified
from the Webkit LICENSE:
https://codereview.chromium.org/1734613003/patch/30001/5637564006400000
https://codereview.chromium.org/1734613003/patch/30001/5670377556541440

[brettw, 2016-03-01 22:39:08]

lgtm

[Johann, 2016-03-02 01:29:07]

The CQ bit was checked by johannkoenig@google.com

[Johann, 2016-03-02 01:29:09]

The CQ bit was unchecked by johannkoenig@google.com

[Johann, 2016-03-02 01:29:16]

The CQ bit was checked by johannkoenig@google.com to run a CQ dry run

[commit-bot: I haz the power, 2016-03-02 01:29:54]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1734613003/30001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1734613003/30001

[commit-bot: I haz the power, 2016-03-02 03:47:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-02 03:47:49]

Dry run: This issue passed the CQ dry run.

[Paweł Hajdan Jr., 2016-03-02 08:53:26]

LGTM

[Johann, 2016-03-02 13:44:20]

The CQ bit was checked by johannkoenig@google.com

[commit-bot: I haz the power, 2016-03-02 13:44:39]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1734613003/30001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1734613003/30001

[commit-bot: I haz the power, 2016-03-02 13:54:42]

Description was changed from

==========
Move libvpx_new to libvpx

The move to libvpx_new happened before M47 (landed in 2524, M47 branch was
2526):
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable so is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

to

==========
Move libvpx_new to libvpx

The move to libvpx_new happened before M47 (landed in 2524, M47 branch was
2526):
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable so is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

[commit-bot: I haz the power, 2016-03-02 13:54:45]

Committed patchset #4 (id:30001)

[commit-bot: I haz the power, 2016-03-02 13:55:41]

Description was changed from

==========
Move libvpx_new to libvpx

The move to libvpx_new happened before M47 (landed in 2524, M47 branch was
2526):
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable so is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)
==========

to

==========
Move libvpx_new to libvpx

The move to libvpx_new happened before M47 (landed in 2524, M47 branch was
2526):
crbug.com/481034
https://codereview.chromium.org/1323333002

Clients which try to transition directly between the tree after this change and
before the previous move will end up in a very broken state.

Now it is 6 months later and M48 is stable so is unlikely that a client would
check out the old code at all, much less try to transition directly between the
two versions.

Leave a compatibility layer for targets which need to be updated out of band
(webrtc, libyuv)

Committed: https://crrev.com/8cdf034791388299f18fba186f2941313320b706
Cr-Commit-Position: refs/heads/master@{#378739}
==========

[commit-bot: I haz the power, 2016-03-02 13:55:44]

Patchset 4 (id:??) landed as
https://crrev.com/8cdf034791388299f18fba186f2941313320b706
Cr-Commit-Position: refs/heads/master@{#378739}