From: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] bash-completion: add recipe
Date: Fri, 13 Dec 2013 16:01:05 +0100 [thread overview]
Message-ID: <1386946865-18483-1-git-send-email-Matthieu.Crapet@ingenico.com> (raw)
---
.../bash-completion/bash-completion_2.0.bb | 31 ++++++++++++++++++++++
1 file changed, 31 insertions(+)
create mode 100644 meta/recipes-support/bash-completion/bash-completion_2.0.bb
diff --git a/meta/recipes-support/bash-completion/bash-completion_2.0.bb b/meta/recipes-support/bash-completion/bash-completion_2.0.bb
new file mode 100644
index 0000000..f08988a
--- /dev/null
+++ b/meta/recipes-support/bash-completion/bash-completion_2.0.bb
@@ -0,0 +1,31 @@
+DESCRIPTION = "Programmable Completion for Bash 4"
+HOMEPAGE = "http://bash-completion.alioth.debian.org/"
+BUGTRACKER = "https://alioth.debian.org/projects/bash-completion/"
+
+SECTION = "console/utils"
+RDEPENDS_${PN} = "bash"
+PR = "r1"
+
+SRC_URI="http://bash-completion.alioth.debian.org/files/${BPN}-${PV}.tar.bz2"
+
+SRC_URI[md5sum] = "0d903f398be8c8f24bc5ffa6f86127f8"
+SRC_URI[sha256sum] = "e5a490a4301dfb228361bdca2ffca597958e47dd6056005ef9393a5852af5804"
+
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
+
+inherit allarch autotools
+
+do_configure() {
+ oe_runconf
+}
+
+do_install_append() {
+ install -d ${D}${sysconfdir}/bash_completion.d/
+ echo '. ${datadir}/${BPN}/bash_completion' >${D}${sysconfdir}/bash_completion
+}
+
+# Some recipes are providing ${PN}-bash-completion packages
+PACKAGES_prepend += "${PN}-extra "
+FILES_${PN}-extra = "${datadir}/${BPN}/completions/ \
+ ${datadir}/${BPN}/helpers/"
--
1.8.2.1
next reply other threads:[~2013-12-13 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 15:01 Matthieu Crapet [this message]
2013-12-13 16:27 ` [PATCH] bash-completion: add recipe Saul Wold
2013-12-13 16:36 ` Paul Eggleton
2013-12-16 8:48 ` Matthieu CRAPET
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=1386946865-18483-1-git-send-email-Matthieu.Crapet@ingenico.com \
--to=matthieu.crapet@ingenico.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