From: Janis Coders <janis.coders@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: [meta-freesclae] Replace/change/append SRC_URI for kernel git URL.
Date: Fri, 08 Nov 2013 12:35:21 +0200 [thread overview]
Message-ID: <527CBE69.30501@gmail.com> (raw)
In-Reply-To: <CAP9ODKpud_q1oD4Ju_y04DPu-Jam6nT4Ok4mRcYUTjD6EFrfBw@mail.gmail.com>
Hmm seems like this worked in the end too:
NEW_SRC_URI = "git://X.X.X.X/git/be-kernel.git;protocol=git;branch=yyyyyyy"
SRC_URI_prepend_mx5 = "${NEW_SRC_URI}"
My git URI is now first in the list and looks like then is priority. Not
really sure what bitbake does on multiple git sources. Seems like
the first one is only used. Is that right?
On 11/06/2013 01:46 PM, Otavio Salvador wrote:
> On Wed, Nov 6, 2013 at 6:12 AM, Janis Coders <janis.coders@gmail.com> wrote:
>> Hi, I am trying to append SRC_URI of linux-imx_2.6.35.3.bb recipe, because
>> we have our own git repository. The problem is that I don't want to override
>> the SRC_URI completely, but only change the git repo address to our server.
>> Does Yocto support it in some pretty way? (because for now we have to use
>> this regex syntax in .bbapend file, which works, but isn't pretty):
>>
>> NEW_SRC_URI = "git://X.X.X.X/git/be-kernel.git;protocol=git;branch=yyyyyyy"
>> TMP_SRC_URI := '${@bb.utils.re.sub("git://[^\\s]*", d.getVar("NEW_SRC_URI",
>> True), d.getVar("SRC_URI", True))}'
>> SRC_URI_mx5 = "${TMP_SRC_URI}"
> I'd write one linux-mycompany recipe or so; but you can use:
>
> oe.util.str_filter_out for it ;-)
>
next prev parent reply other threads:[~2013-11-08 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 8:12 [meta-freesclae] Replace/change/append SRC_URI for kernel git URL Janis Coders
2013-11-06 11:46 ` Otavio Salvador
2013-11-08 10:35 ` Janis Coders [this message]
2013-11-08 11:12 ` Otavio Salvador
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=527CBE69.30501@gmail.com \
--to=janis.coders@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.