Openembedded Core Discussions
 help / color / mirror / Atom feed
From: brian avery <brian.avery@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] testsdk: use cpio instead of cvs as test
Date: Sat, 18 Mar 2017 08:05:29 -0700	[thread overview]
Message-ID: <cover.1489849183.git.brian.avery@intel.com> (raw)

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


--
1.9.1


             reply	other threads:[~2017-03-18 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 15:05 brian avery [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-18 15:08 [PATCH 0/2] testsdk: use cpio instead of cvs as test brian avery

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1489849183.git.brian.avery@intel.com \
    --to=brian.avery@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox