From: akuster808 <akuster808@gmail.com>
To: qianl.fnst@cn.fujitsu.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] tomoyo-tools: Add new recipes
Date: Tue, 11 Nov 2014 21:32:17 -0800 [thread overview]
Message-ID: <5462F0E1.1020308@gmail.com> (raw)
In-Reply-To: <1415353882-20874-1-git-send-email-qianl.fnst@cn.fujitsu.com>
Do we need two TOMOYO solutions?
Meta-security has ccs-tools 1.8.3.
- Armin
On 11/7/14, 1:51 AM, Qian Lei wrote:
> TOMOYO Linux is a Mandatory Access Control (MAC) implementation for
> Linux that can be used to increase the security of a system, while also
> being useful purely as a system analysis tool.
>
> Signed-off-by: Qian Lei <qianl.fnst@cn.fujitsu.com>
> ---
> .../tomoyo-tools/tomoyo-tools_2.5.0.bb | 29 ++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 meta-oe/recipes-support/tomoyo-tools/tomoyo-tools_2.5.0.bb
>
> diff --git a/meta-oe/recipes-support/tomoyo-tools/tomoyo-tools_2.5.0.bb b/meta-oe/recipes-support/tomoyo-tools/tomoyo-tools_2.5.0.bb
> new file mode 100644
> index 0000000..bb2676b
> --- /dev/null
> +++ b/meta-oe/recipes-support/tomoyo-tools/tomoyo-tools_2.5.0.bb
> @@ -0,0 +1,29 @@
> +SUMMARY = "TOMOYO Linux tools"
> +DESCRIPTION = "TOMOYO Linux is a Mandatory Access Control (MAC) implementation \
> +for Linux that can be used to increase the security of a system, while also \
> +being useful purely as a system analysis tool."
> +HOMEPAGE = "http://tomoyo.sourceforge.jp/"
> +SECTION = "System Environment/Kernel"
> +
> +SRC_URI = "http://jaist.dl.sourceforge.jp/tomoyo/53357/${PN}-${PV}-20140601.tar.gz"
> +SRC_URI[md5sum] = "888869b793127f00d6439a3246598b83"
> +SRC_URI[sha256sum] = "118ef6ba1fbf7c0b83018c3a0d4d5485dfb9b5b7f647f37ce9f63841a3133c2a"
> +
> +S = "${WORKDIR}/${PN}"
> +
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING.tomoyo;md5=751419260aa954499f7abaabaa882bbe"
> +
> +FILES_${PN} += "${libdir}/tomoyo"
> +FILES_${PN}-dbg += "${libdir}/tomoyo/.debug"
> +
> +DEPENDS = "linux-libc-headers ncurses"
> +CFLAGS_append += "-D_GNU_SOURCE"
> +
> +do_compile () {
> + oe_runmake 'CC=${CC}'
> +}
> +
> +do_install() {
> + oe_runmake install INSTALLDIR=${D}
> +}
>
prev parent reply other threads:[~2014-11-12 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 9:51 [PATCH] tomoyo-tools: Add new recipes Qian Lei
2014-11-12 5:32 ` akuster808 [this message]
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=5462F0E1.1020308@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=qianl.fnst@cn.fujitsu.com \
/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