From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patching from a file containing a compressed directory (<directory>.tar.bz2)
Date: Wed, 26 Jan 2011 23:57:12 +0100 [thread overview]
Message-ID: <4D40A6C8.8020705@atmel.com> (raw)
In-Reply-To: <4D4092E8.8040207@atmel.com>
2011-01-26 22:32, Ulf Samuelsson skrev:
> Trying to change the at91 linux recipes.
> The "experimental" patches to be added on top of the "maxim" patch
> can be downloaded from ftp://ftp.at91.com/ and that file
> is generated from a directory of patches, which should be applied
> in alphabetical order.
>
> When the "obvious" SRC_URI is used:
>
> ftp://ftp.at91.com/<directory>.tar.bz2;apply=yes \
>
> the files do not get applied in alphabetical order.
>
> It looks to me like they get applied in reverse order, but I did
> not check carefully.
> I tried adding a "series" file, and recompress, but that failed as
> well.
>
> Any clue on how to get the patches applied in alphabetical order?
>
> If the patches are in a subdirectory to the recipe, and applied
> manually
> everything is OK, but that seems to be a shame to have to resort
> to that.
>
BTW: I figured out that I can avoid applying the file as a patch,
and just let the file be decompressed to ${WORKDIR}, and then
apply the patches manually in a "do_patch_prepend" function.
Drawback is that if there are working patches before this,
then they also need to be applied manually.
Seems strange that the patches are not applied in alphabetical order.
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2011-01-26 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 21:32 Patching from a file containing a compressed directory (<directory>.tar.bz2) Ulf Samuelsson
2011-01-26 22:57 ` Ulf Samuelsson [this message]
2011-01-27 0:19 ` Koen Kooi
2011-01-27 23:17 ` Ulf Samuelsson
2011-01-28 1:07 ` Chris Larson
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=4D40A6C8.8020705@atmel.com \
--to=ulf.samuelsson@atmel.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 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.