testsdk: use cpio instead of cvs as test

We were using cvs as our sdk test by running configure,make, and install using the sdk. Unfortunately, cvs requires vi and we were therefore requiring vi as one of our HOSTTOOLS. Since this is a choice among many for editors, it makes for a fragile requirement. Furthermore, a build container would typically not have an editor in it but should still be able to build and test images. This patch switches cpio (also autotools based and so checks the same steps) for cvs, thus dropping the vi requirement.

-brian

The following changes since commit 7e0985bab68547f946163828a16beab7542fca2e:

nativesdk-packagegroup-sdk-host.bb: add cmake (2017-03-17 16:53:06 +0000)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib bavery/changeCVSTestToCpioTest
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/changeCVSTestToCpioTest

brian avery (2):
meta/lib/oeqa: change sdk test from cvs to cpio
bitbake.conf: remove vi from HOSTTOOLS list

 meta/classes/testimage.bbclass                            | 6 +++---
 meta/conf/bitbake.conf                                    | 2 +-
 meta/lib/oeqa/runtime/cases/{buildcvs.py => buildcpio.py} | 8 ++++----
 meta/lib/oeqa/sdk/cases/{buildcvs.py => buildcpio.py}     | 8 ++++----
 4 files changed, 12 insertions(+), 12 deletions(-)
 rename meta/lib/oeqa/runtime/cases/{buildcvs.py => buildcpio.py} (83%)
 rename meta/lib/oeqa/sdk/cases/{buildcvs.py => buildcpio.py} (80%)

--
1.9.1