From: Matthieu Crapet <mcrapet@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH v2] plowshare: Add Git version (initial recipe)
Date: Wed, 15 Aug 2012 10:43:39 +0200 [thread overview]
Message-ID: <502B613B.4020200@gmail.com> (raw)
In-Reply-To: <502A8D7E.1000009@communistcode.co.uk>
Hi,
Thanks for answer! The path in the "diff --git" line is not good.
"meta-openembedded-contrib/meta-oe/recipes-support" is my suggestion.
However, I don't know if this kind of software is suitable for oe-devel.
I just wanted to create a "valid" recipe.
I'm still confused with this SRCREV thing. Just want to retrieve HEAD
from git master branch. Also tried using inherit gitpkgv
(like systemd) but It raises an error without SRCREV defined.
Regards,
Matthieu
PS: What's the difference between:
https://github.com/openembedded/meta-oe
http://cgit.openembedded.org/meta-openembedded/
>
> 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
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-08-15 8:57 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
2012-08-15 8:43 ` Matthieu Crapet [this message]
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=502B613B.4020200@gmail.com \
--to=mcrapet@gmail.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