From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: chris_larson@mentor.com, openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/1] classes/patch: return "other" elements found on the SRC_URI
Date: Wed, 1 Feb 2012 09:42:45 -0500 [thread overview]
Message-ID: <1328107366-22541-1-git-send-email-bruce.ashfield@windriver.com> (raw)
Richard,
When working with Tom on some BSP usability cases, he noted that it was nice
that we can specify more complex features in the SRC_URI now that patch
ordering and location is maintained by using the src_patches abstraction that
Chris added to patch.bbclass. But .. there's always a but, you had to
specify some sort of patch to trigger the processing.
Rather than hack something in that is specific to linux-yocto, it seemed
like a good idea to add the ability to get 'anything that isn't a patch'
from the same routines that Chris added to patch.bbclass.
I'm now using this support to pickup all sorts of things from the SRC_URI,
without knowing anything about the format of the SRC_URI itself. Extra
filtering on 'other' is the responsibility of the caller.
I'm not the worlds top python coder yet, so I'm sure there are better ways
to do this, hence why I'm calling this an RFC patch. I can re-work it
as appropriate to get it into the tree, and I'll follow up with my user
of the new functionality.
Cheers,
Bruce
cc: Chris Larson <chris_larson@mentor.com>
next reply other threads:[~2012-02-01 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 14:42 Bruce Ashfield [this message]
2012-02-01 14:42 ` [PATCH] classes/patch: return "other" elements found on the SRC_URI Bruce Ashfield
2012-02-01 15:52 ` Richard Purdie
2012-02-01 15:56 ` Bruce Ashfield
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=1328107366-22541-1-git-send-email-bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox