Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC PATCHv2] bash-completion: add recipe
Date: Mon, 16 Dec 2013 11:07:37 +0100	[thread overview]
Message-ID: <l8mj8n$bv2$1@ger.gmane.org> (raw)
In-Reply-To: <1387183299-7468-1-git-send-email-Matthieu.Crapet@ingenico.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthieu Crapet schreef op 16-12-13 09:41:
> This new recipe discards the old recipe in OE-Classic: 
> http://layers.openembedded.org/layerindex/oe-classic/recipe/16369/
> 
> When building ready-to-use images (like .vmdk), it is sometimes
> convenient to have a fancy shell environment.
> 
> Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> --- 
> .../bash-completion/bash-completion_2.0.bb         | 31
> ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode
> 100644 meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb
> 
> diff --git
> a/meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb
> b/meta-oe/recipes-support/bash-completion/bash-completion_2.0.bb new file
> mode 100644 index 0000000..c70d988 --- /dev/null +++
> b/meta-oe/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/" + +LICENSE =
> "GPLv2" +LIC_FILES_CHKSUM =
> "file://COPYING;md5=751419260aa954499f7abaabaa882bbe" + +SECTION =
> "console/utils" +RDEPENDS_${PN} = "bash"

R* vars go below do_install

> +PE = "1"

New recipe, so drop PE

> + 
> +SRC_URI="http://bash-completion.alioth.debian.org/files/${BPN}-${PV}.tar.bz2"
>
> 
+
> +SRC_URI[md5sum] = "0d903f398be8c8f24bc5ffa6f86127f8" +SRC_URI[sha256sum]
> = "e5a490a4301dfb228361bdca2ffca597958e47dd6056005ef9393a5852af5804" + 
> +inherit allarch autotools + +do_configure() { +	oe_runconf +}

Can you add a comment why autotools_do_configure fails?

> + +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 "

PACKAGES =+ "${PN}-extra"

> +FILES_${PN}-extra = "${datadir}/${BPN}/completions/ \ +
> ${datadir}/${BPN}/helpers/"
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFSrtDpMkyGM64RGpERAoQpAJ4vfbU5Q0laNx8W61aMEEfao8gtfwCggn2l
mJXDKKcx/uPPjhiEDZhc7LE=
=IlfI
-----END PGP SIGNATURE-----



      reply	other threads:[~2013-12-16 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16  8:41 [RFC PATCHv2] bash-completion: add recipe Matthieu Crapet
2013-12-16 10:07 ` Koen Kooi [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='l8mj8n$bv2$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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