From: Denys Dmytriyenko <denys@ti.com>
To: "Devshatwar, Nikhil" <nikhil.nd@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: Applying non local patches
Date: Mon, 1 Dec 2014 16:49:38 -0500 [thread overview]
Message-ID: <20141201214937.GE5113@edge> (raw)
In-Reply-To: <E60A9E1B4132A24DB80BD56ABC926847D2DB79@DBDE04.ent.ti.com>
On Fri, Nov 14, 2014 at 01:02:09PM +0000, Devshatwar, Nikhil wrote:
> Hi all,
> Does yocto support applying patches which are under review
> It is possible to download the patch and add it to the recipe along with the actual patch file
>
> But is there another way where we can point to the patches in the SRC_URI itself
>
> Something similar to
>
> SRC_URI= "git:git.fredesktop.org/project/repo.git;protocol=git \
> http://patchwork.freedesktop/project/repo/12345/raw;protocol=http \
> "
> Are there any examples of such reciepes
> Please help
Nikhil,
It's not recommended, but it was always possible. Here's an old example from
OE Classic, as I couldn't find any recent one:
http://cgit.openembedded.org/openembedded/tree/recipes/busybox/busybox_1.7.2.bb
We moved away from that practice, as upstream used to constantly tweak and
change patches, breaking the build all the time. Having patches in metadata
gives more control, as updating patches, their checksums and making sure the
build doesn't break can be done at the same time.
--
Denys
next prev parent reply other threads:[~2014-12-01 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 13:02 Applying non local patches Devshatwar, Nikhil
2014-12-01 21:49 ` Denys Dmytriyenko [this message]
2014-12-02 7:08 ` Devshatwar, Nikhil
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=20141201214937.GE5113@edge \
--to=denys@ti.com \
--cc=meta-arago@arago-project.org \
--cc=nikhil.nd@ti.com \
/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.