summaryrefslogtreecommitdiff
path: root/classes/patch.bbclass
AgeCommit message (Collapse)AuthorFiles
2009-08-24patch.bbclass: Add "git" patchtool mechanism, which uses git-applyDale Farnsworth1
It can be selected by setting PATCHTOOL = "git". This is useful because git-apply honors the permissions information produced by git-format-patch. Signed-off-by: Dale Farnsworth <dfarnsworth@mvista.com> Signed-off-by: Chris Larson <clarson@mvista.com> Acked-by: Denys Dmytriyenko <denis@denix.org>
2009-05-14Shorten some full paths printed to the user.Chris Larson1
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>
2009-05-12patch.bbclass: use hashlib with Python 2.5+ - removes DeprecationWarningMarcin Juszkiewicz1
2008-05-24patch.bbclass: Simplify patch task dependency handling and allow packages to ↵Richard Purdie1
override the dependency more easily (from poky)
2008-01-28patch.bbclass: Show full path of a patch.Paul Sokolovsky1
* This is for consistency with existing non-patch fetch message in base.bbclass. Allows to catch pulling file from wrong override dir quickly.
2007-08-03patch.bbclass: give empty file for quilt so it will not use config from user ↵Marcin Juszkiewicz1
homedir - closes #2704 (code from Poky)
2007-08-03patch.bbclass: Add minrev and maxrev support for patches, cleanup maxdate ↵Richard Purdie1
and mindate support
2007-05-11devshell.bbclass, patch.bbclass: Error on any non-zero rc from TERMCMD*.Paul Sokolovsky1
* Suggested by Richard Purdie. * Closes #2274.
2007-05-11devshell.bbclass, patch.bbclass: Check exit code of TERMCMD* commands to see ↵Paul Sokolovsky1
if they were found at all. * Fixes #2274.
2007-04-18classes: Add support for intertask dependencies to be specified, needed for ↵Richard Purdie1
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.
2007-04-09patch.bbclass/devshell.bbclass: Switch to new form of interactive task ↵Richard Purdie1
handling as per RFC which is more compatible with bitbake 1.8+
2007-03-31classes/patch.bbclass: Make sure to raise func_failed on any exception from ↵Holger Freyther1
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.
2006-12-06patch.bbclass: Fix errors when reapplying patchesRichard Purdie1
2006-09-05patch.bbclass: Fix bug in PatchTree.Import resulting in new patches being ↵Chris Larson1
imported -before- the current patch rather than -after-.
2006-09-05patch.bbclass: fix issue encountered by zecke, where PatchTree was only ↵Chris Larson1
doing a --dry-run, never actually applying the patch. Only quilt-native in oe was using that.
2006-08-30patch.bbclass:Chris Larson1
* 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.
2006-08-30patch.bbclass:Chris Larson1
* 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.
2006-08-30classes/patch.bbclass: Create a "patches" directory when initialisingJamie Lenehan1
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.
2006-08-28Merge from poky:Chris Larson1
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.