From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH v2] plowshare: Add Git version (initial recipe)
Date: Tue, 14 Aug 2012 18:40:14 +0100 [thread overview]
Message-ID: <502A8D7E.1000009@communistcode.co.uk> (raw)
In-Reply-To: <CAL2sKTm8xG5o7MfWiALcXrzTsvqk-vR0VmkJbC4Wt4ecCZVxPQ@mail.gmail.com>
On 14/08/2012 13:50, Matthieu wrote:
> Add recipe for plowshare (git repository).
>
> v2:
> - fix big mistake DEPENDS => RDEPENDS
> - set SRCREV to empty string
> - keep PE=1 to respect upstream scheme
>
> Signed-off-by: Matthieu Crapet <mcrapet@gmail.com>
> ---
> meta/recipes-support/plowshare/plowshare_git.bb | 27
> +++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 meta/recipes-support/plowshare/plowshare_git.bb
>
> diff --git a/meta/recipes-support/plowshare/plowshare_git.bbb/meta/recipes-support/plowshare/
> plowshare_git.bb
> new file mode 100644
> index 0000000..f819255
> --- /dev/null
> +++ b/meta/recipes-support/plowshare/plowshare_git.bb
> @@ -0,0 +1,27 @@
> +DESCRIPTION = "Command-line download/upload tool for file sharing hosters"
> +HOMEPAGE = "http://code.google.com/p/plowshare/"
> +SECTION = "console/utils"
> +
> +LICENSE = "GPLv3"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> +
> +# Follow uptream (debian) naming convention,
> +# for example: plowshare_1~git20120807-1_all.deb
> +PV = "gitr${SRCPV}"
> +PE = "1"
> +SRCREV = ""
> +
> +RDEPENDS_${PN} = "bash curl"
> +SRC_URI = "git://
> code.google.com/p/plowshare.git;protocol=http;branch=master"
> +S = "${WORKDIR}/git"
> +
> +inherit allarch
> +
> +# Nothing to compile, it's scripts!
> +do_compile() {
> + :
> +}
> +
> +do_install() {
> + oe_runmake PREFIX="${prefix}" DESTDIR="${D}" install
> +}
> --
> 1.7.9.5
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Matthieu,
Before you bear the wrath of Koen, I would recommend you at least move
this to an appropriate layer (such as somewhere in meta-oe[1]).
The general consensus is that things only go in oe-core if they are
required for a core-system build.
[1] https://github.com/openembedded/meta-oe
next prev parent reply other threads:[~2012-08-14 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 9:48 [RFC][PATCH] plowshare: Add Git version (initial recipe) Matthieu
2012-08-14 9:57 ` Koen Kooi
2012-08-14 12:50 ` [RFC][PATCH v2] " Matthieu
2012-08-14 17:40 ` Jack Mitchell [this message]
2012-08-15 8:43 ` Matthieu Crapet
2012-08-15 8:53 ` Koen Kooi
2012-08-15 9:27 ` Paul Eggleton
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=502A8D7E.1000009@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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