From: Peter Urbanec <openembedded-devel@urbanec.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gstreamer1.0*git: Update to build current AUTOREV from master branch.
Date: Fri, 27 Feb 2015 13:52:40 +1100 [thread overview]
Message-ID: <54EFDBF8.6030808@urbanec.net> (raw)
In-Reply-To: <1424987142.26813.40.camel@linuxfoundation.org>
On 27/02/15 08:45, Richard Purdie wrote:
>> +inherit gitpkgv
>
> The gitpkgv class isn't in OE-Core, nor is it going to be (this has been
> discussed on the mailing list before). As such if we merge this, OE-Core
> won't parse, let alone build.
Does that mean that no packages in oe-core can currently support a clean
and consistent AUTOREV?
If that is the case, would it make more sense to leave the release
versions of gstreamer in oe-core and move the git versions to oe-meta
where I can use the current implementation of gitpkgv?
next prev parent reply other threads:[~2015-02-27 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 17:57 [PATCH] gstreamer1.0*git: Update to build current AUTOREV from master branch Peter Urbanec
2015-02-26 21:45 ` Richard Purdie
2015-02-27 2:52 ` Peter Urbanec [this message]
2015-02-26 21:52 ` Burton, Ross
2015-02-27 3:06 ` Peter Urbanec
2015-02-27 9:35 ` Andreas Oberritter
2015-02-27 12:27 ` Peter Urbanec
2015-02-27 13:58 ` Martin Jansa
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=54EFDBF8.6030808@urbanec.net \
--to=openembedded-devel@urbanec.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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