openembedded-core.git/meta/classes/patch.bbclass, branch morty

lib/oe/patch: commit with a dummy user/email when PATCHTOOL=git

2016-09-03T08:58:45+00:00

When using PATCHTOOL = "git", the user of the system is not really the
committer - it's the build system itself. Thus, specify "dummy" values
for username and email instead of using the user's configured values.
Various parts of the devtool code that need to make commits have also
been updated to use the same logic.

This allows PATCHTOOL = "git" and devtool to be used on systems where
git user.name / user.email has not been set (on versions of git where
it doesn't default a value under this circumstance).

If you want to return to the old behaviour where the externally
configured user name / email are used, set the following in your
local.conf:

PATCH_GIT_USER_NAME = ""
PATCH_GIT_USER_EMAIL = ""

Fixes [YOCTO #8703].

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

patch.bbclass: remove useless path assignment

2016-04-05T22:12:41+00:00

A path variable is assigned the value of PATH from the
environment, before the PATH is set on the environemnt
from the value of PATH in the bb datastore. This seems
to be an unnecessary leftover.

[YOCTO #8543]

Signed-off-by: Alex Franco 
Signed-off-by: Richard Purdie

patch.bbclass: unset TMPDIR after use

2014-06-29T07:58:30+00:00

GNU Patch < 2.6.1 has a race condition so we create a per-instance TMPDIR to
avoid this.  This was implemented by setting os.environ[TMPDIR] but at the end
of do_patch the temporary directory is deleted but TMPDIR is not unset.

In general this doesn't cause a problem but if do_patch is embedded in a larger
function then TMPDIR is set to a directory that doesn't exist.  Avoid this by
removing TMPDIR from os.environ when the directory is deleted.

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

meta: Don't use deprecated bitbake API

2013-09-01T14:51:36+00:00

These have been deprecated for a long time, convert the remaining
references to the correct modules and prepare for removal of the
compatibility support from bitbake.

Signed-off-by: Richard Purdie

patch.bbclass: increase security

2012-09-14T16:05:04+00:00

- Use mkdtemp for generating temp dir names
- Use bb.utils.remove for removing temp dirs
- Add comment for explaining the "patch" workaround

[YOCTO #3070]

Signed-off-by: Constantin Musca 
Signed-off-by: Richard Purdie

patch.bbclass: Use one TMPDIR per patching process

2012-09-14T08:49:53+00:00

We must use one TMPDIR per process (/tmp/${PID}) so that the patching
processes don't generate the same temp file name (the "patch" program
uses the TMPDIR environment variable for deciding where to create the
temp files).

[YOCTO #3070]

Signed-off-by: Constantin Musca 
Signed-off-by: Saul Wold

Convert tab indentation in python functions into four-space

2012-07-19T09:17:30+00:00

Signed-off-by: Richard Purdie

quilt: move empty quiltrc to native sysconfdir

2012-04-24T14:51:35+00:00

patch.bbclass orignally pointed at /usr/bin/quiltrc for an empty
version to ensure that no user setting were picked up, change this
to /etc/quiltrc in the Native sysroot since we now have a native
sysconfdir.

Make sure that the quiltrc is actually installed in the Native
sysconfdir, not the target, so fix this after the recipe split.

Signed-off-by: Saul Wold

classes/patch: optionally return non-patch sources

2012-02-03T16:51:30+00:00

commit:

  patch.bbclass: abstract out logic that determines patches to apply

gives the ability for other clases to emit series files for use outside
of a build system, or even within the build system. There are sometimes
elements on the SRC_URI that while not directly applicable to patching,
can be related to patching the package. For example, the yocto kernel
class would like to know about these other source items on the SRC_URI
to locate out of tree kernel features.

This change keeps the default behaviour of returning patches, but adds the
ability to request that non-patch results be returned.  Additional filtering
within the non-patch category, is left up to the caller of the routine.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

classes/patch: avoid backtrace when patch does not apply

2012-01-19T14:32:04+00:00

We don't need to see a Python stack backtrace when a patch does not
apply, just the error output from patch, so trap these kinds of errors
and ensure that we display the message and fail the task and nothing
else.

Fixes [YOCTO #1143]

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie