[OE-core] [PATCH] gstreamer1.0-omx: use mulitple SCMs to fetch submodules

[Belal, Awais]

Hi Nicolas,

I sent this against the omx package only because I wanted to see if there's any feedback on this for improvement or anything that I might be doing wrong. If this gets accepted I will submit updates for the other gstreamer1.0-*_git.bb recipes as you've correctly pointed out that they suffer from the same dilemma. Doing it through a .inc wouldn't be a good idea because the dependency from one package to the other lies not just only the package but the exact rev as well so it should be done in this way for all in my opinion.

The SRC_REVs will obviously need to be taken care of when an update is made but I think this is the way to go. 

BR,
Awais

________________________________________
From: Nicolas Dechesne [nicolas.dechesne at linaro.org]
Sent: Monday, December 29, 2014 5:41 PM
To: Belal, Awais
Cc: Patches and discussions about the oe-core layer
Subject: Re: [OE-core] [PATCH] gstreamer1.0-omx: use mulitple SCMs to fetch submodules

On Mon, Dec 29, 2014 at 10:46 AM, Awais Belal <awais_belal at mentor.com> wrote:
> The gstreamer omx package uses a submodule 'common' which
> is fetched by the configure script. This approach fails
> on non-network builds as the fetcher tries to look upstream
> for the submodule.
> We now use multiple SCMs, one for the main omx package and
> the other for the 'common' submodule so it is available in
> the downloads_dir for later use.
>

we have the same issues with all the others gstreamer1.0-*_git.bb
recipes, don't we? maybe we should fix them all. i am not sure if
there is a nice way to do it for all recipes, like with a .inc file,
to avoid duplication..

also, the autogen.sh script will still run git submodule update, even
if the 'common' folder already exist, so we will need to be extra
careful when upgrading the _git.bb recipes to update both
SRCREV_gst-omx and SRCREV_common or we will have the same issue
again..