From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] patch file location
Date: Tue, 22 Jun 2010 09:30:28 +0200 [thread overview]
Message-ID: <201006220930.31306.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <AANLkTim2-Y4qW9Wb-kycxo89vNZgBJkdeVSyERXZYCoJ@mail.gmail.com>
Dnia wtorek, 22 czerwca 2010 o 09:03:43 Frans Meulenbroeks napisał(a):
> I'd like to draw the attention to the location of patch files.
> My original understanding was that these should be in either the files
> dir (if they apply to all), or in a dir with the name of the recipe
> (replacing the _ with a - ).
>
> And I kind-a assumed that if a patch is in a recipe dir it would have
> priority above a version in the files dir.
This is controlled by FILESPATHPKG and OVERRIDES.
> Frankly speaking I have no clue at all which version of the patch will
> be used by the 2.10.1 recipe.
glibc-2.4/ one - check FILESPATHPKG setting in glibc_2.10.1.bb recipe.
> The only ways to find out is to study the class code that does the patch or
> to actually build the package (in the hope it selects the patch in a
> deterministic way).
I did "grep FILES glibc/*" to find out.
> I don't think it is good that if someone is debugging a problem that they
> should have such a hard time to find out what version of a file is
> actually used
> My proposal:
> - only apply patches (seek for patches) in the recipe dir (e.g. in the
> example for glibc_2.10.1.bb this would be glibc-2.10.1) and in the
> files directory
It is not only patches. It is everything in SRC_URI. And we have this
mechanism since beginning.
> (optionally we might allow for a mechanism that allows specifying
> patches for higher level recipes; e.g. glibc_2.10.1 could look in
> glibc-2.10.1, glibc-2.10, glibc-2, glibc and files).
We have such mechanism already - it is FILESPATHPKG and related vars.
> How do people feel about this? Any implementation hints?
Why implement when it is already implemented?
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2010-06-22 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 7:03 [RFC] patch file location Frans Meulenbroeks
2010-06-22 7:30 ` Marcin Juszkiewicz [this message]
2010-06-22 8:03 ` Frans Meulenbroeks
2010-06-22 8:38 ` Koen Kooi
2010-06-22 9:23 ` Phil Blundell
2010-06-22 10:25 ` Frans Meulenbroeks
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=201006220930.31306.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--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.