From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Fixes for square brackets in installed filenames
Date: Thu, 22 Dec 2016 15:19:55 +1300 [thread overview]
Message-ID: <cover.1482373109.git.paul.eggleton@linux.intel.com> (raw)
When attempting to create a recipe for something that installs files
with square brackets in their name I stumbled across a couple of issues,
here are the fixes.
The following changes since commit 5e21afc9395060b489156d3f90505a372b713f37:
Revert "selftest/wic: extending test coverage for WIC script options" (2016-12-20 17:06:01 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/bracket-fixes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/bracket-fixes
Paul Eggleton (4):
classes/package_rpm: handle square brackets in filenames
lib/oe/path: add warning comment about oe.path.remove() with wildcarded filenames
classes/sstate: handle filenames containing square brackets
classes/sstate: fix file conflict message
meta/classes/package_rpm.bbclass | 6 ++++++
meta/classes/sstate.bbclass | 24 +++++++++++++-----------
meta/lib/oe/path.py | 9 ++++++++-
3 files changed, 27 insertions(+), 12 deletions(-)
--
2.5.5
next reply other threads:[~2016-12-22 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 2:19 Paul Eggleton [this message]
2016-12-22 2:19 ` [PATCH 1/4] classes/package_rpm: handle square brackets in filenames Paul Eggleton
2016-12-22 2:19 ` [PATCH 2/4] lib/oe/path: add warning comment about oe.path.remove() with wildcarded filenames Paul Eggleton
2016-12-22 2:19 ` [PATCH 3/4] classes/sstate: handle filenames containing square brackets Paul Eggleton
2016-12-22 2:19 ` [PATCH 4/4] classes/sstate: fix file conflict message Paul Eggleton
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=cover.1482373109.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@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.