| Age | Commit message (Collapse) | Author | Files |
|---|
|
Adds a base_path_out convenience function, which prepares a full path for
display to the user. The initial implementation just makes it relative to
${TOPDIR}. This function is then used for some messages outputted to the
user (packaged-staging, patch application, clean, unpack tasks).
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
|
|
override the dependency more easily (from poky)
|
|
* This is for consistency with existing non-patch fetch message in base.bbclass.
Allows to catch pulling file from wrong override dir quickly.
|
|
homedir - closes #2704 (code from Poky)
|
|
and mindate support
|
|
* Suggested by Richard Purdie.
* Closes #2274.
|
|
if they were found at all.
* Fixes #2274.
|
|
correct operation with bitbake 1.8.x. Old behaviour is maintained in a special legacy anonymous function in base.bbclass. The patch is an improved version of the one discussed on the mailing list.
|
|
handling as per RFC which is more compatible with bitbake 1.8+
|
|
within Import
non existing patches raised a IOError by the md5sum method which was not
catched at all and lead bitbake to exit due an unhandled exception. This
is bad for all autobuilders.
|
|
|
|
imported -before- the current patch rather than -after-.
|
|
doing a --dry-run, never actually applying the patch. Only quilt-native in oe was using that.
|
|
* switch os.mkdir to os.makedirs.
* pass on all errors from QuiltTree.Clean(), as it can fail in ways that do
not need to be reported to the user, and a failure will end up being seen
again during the Import/Push of the patches.
|
|
* Add NOOPResolver class, which simply passes the patch failure on up, not
doing any actual patch resolution. Set PATCHRESOLVE = "noop" to make use of
it. Most useful for unattended builds.
|
|
the quilt patcher class. Without this quilt will search for a patches
directory - starting from the current directory up to the root
directory. If it finds an existing patches directory it will use it
for its patches. This causes all sorts of problems since it is not
where the patches are expected to be. Prior to the recent patcher
changes this directory was being created.
|
|
Rework the way patches are handled. There are now two abstract base classes,
initialized in patch.bbclass. One for patchset operations on a directory, and
another for patch failure resolution. Currently includes 'patch' and 'quilt'
concrete PatchSet classes, and a 'user' resolver class, which simply drops you
into a shell in the source tree to fix the rejects.
|
