From: <kai.kang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH 0/2] Add recipes of cfengine and its dependency tokyocabinet
Date: Mon, 18 Jul 2016 09:06:04 +0800 [thread overview]
Message-ID: <1468803966-9809-1-git-send-email-kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
Kai Kang (2):
tokyocabinet: add recipe
cfengine: add recipe and base policy
.../remove-policy-of-usr-local-sbin.patch | 28 +++++++++
.../cfengine/cfengine-masterfiles_3.9.0.bb | 37 +++++++++++
.../cfengine/change-hard-coded-lib-path.patch | 28 +++++++++
.../cfengine/set-path-of-default-config-file.patch | 23 +++++++
.../recipes-extended/cfengine/cfengine_3.9.0.bb | 71 ++++++++++++++++++++++
.../remove-hard-coded-include-and-lib-paths.patch | 43 +++++++++++++
.../tokyocabinet/tokyocabinet_1.4.48.bb | 27 ++++++++
7 files changed, 257 insertions(+)
create mode 100644 meta-oe/recipes-extended/cfengine/cfengine-masterfiles/remove-policy-of-usr-local-sbin.patch
create mode 100644 meta-oe/recipes-extended/cfengine/cfengine-masterfiles_3.9.0.bb
create mode 100644 meta-oe/recipes-extended/cfengine/cfengine/change-hard-coded-lib-path.patch
create mode 100644 meta-oe/recipes-extended/cfengine/cfengine/set-path-of-default-config-file.patch
create mode 100644 meta-oe/recipes-extended/cfengine/cfengine_3.9.0.bb
create mode 100644 meta-oe/recipes-support/tokyocabinet/tokyocabinet/remove-hard-coded-include-and-lib-paths.patch
create mode 100644 meta-oe/recipes-support/tokyocabinet/tokyocabinet_1.4.48.bb
--
2.6.1
next reply other threads:[~2016-07-18 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 1:06 kai.kang [this message]
2016-07-18 1:06 ` [PATCH 1/2] tokyocabinet: add recipe kai.kang
2016-07-18 1:06 ` [PATCH 2/2] cfengine: add recipe and base policy kai.kang
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=1468803966-9809-1-git-send-email-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-devel@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