| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
|
|
|
|
We'll be skipping the Pending Deprecation step given our release process.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
(From Poky rev: d7eebbe9dbf0d790d4af93466f5c27127cae0999)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
It's cleaner to leave it behaving as usual, passing the exception data in the
exc_info attribute of the LogRecord where it normally lies, and then let
LogHandler make it pickleable so it can be sent to the UI.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
It turns out that while log filters added with addFilter are only associated
with that logger, and not its children, handlers are inherited, and handlers
can be filters. So, let's add filtering to our existing LogHandler class
which dispatches our log records as bitbake events.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
(From Poky rev: af06e4a8efbcaff657c397c34f2cb893d2d7f7f7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
BBLogRecords)
This allows us to identify which task messages are from.
(From Poky rev: f8e7215f6c4ece8c0a74ceee8da707cf791038e8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
This is a compatibility measure, as previous versions did not error out when
this occurred, and will most likely be dropped in the next bitbake minor
version in favor of a fatal error.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
We use a custom Logger subclass for our loggers
This logger provides:
- 'debug' method which accepts a debug level
- 'plain' method which bypasses log formatting
- 'verbose' method which is more detail than info, but less than debug
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
This is necessary, as there has not yet been a release with the bb.utils
versions in place. We can't show them a deprecation warning when they can't
safely change it yet. Show a PendingDeprecationWarning until 1.10 releases
and OE requires it, then we can move to DeprecationWarning.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
This ensures the check is run for anyone using the package, including
setup.py, though it's sad that it's necessary, since all it really wants is
__version__.
Ideally, we'd avoid the version check entirely in favor of checking for
functionality, but that's rather difficult with language constructs like
context managers, so this'll do for now.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
As an example, this displays a deprecation warning for the use of
"bb.encodeurl" when you should be using "bb.fetch.encodeurl". It includes a
convenience function for this purpose. It should be of use when moving
objects between modules permanently, changing the API the user sees.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
We should add back in some proper unit testing. Doctest is rather limited,
and we haven't actually made use of it since the original implementation of
the datastore when the project started, as far as I'm aware.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
This is just for compatibility. We may drop it in the future, or rewrite it,
as it's not particularly pythonic.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
The following utility functions were removed. Note that in this particular
case we're bypassing a proper deprecation process, as these functions are
clearly not utilized, are obvious remnants of old ways of doing things, and
some of which do not even function properly.
- tokenize
- evaluate
- flatten
- relparse
- ververify
- isjustname
- isspecific
- catpkgsplit
- pkgsplit
- pkgcmp
- dep_parenreduce
- dep_opconvert
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
<petri.lehtinen+bitbake-dev@inoi.fi>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
In preparation for python3.0 make sure our test cases
are working again.
|
|
|
|
movefile error reporting)
|
|
decoded to host="" (#1530)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- those scripts are not called by hand by bitbake users
and most of package linting tools (lintian/Debian, rpmlint/Fedora)
complain about not executable scripts.
- if someone want to run them by hand then he will be able to do it
with calling 'python SCRIPT'
|
|
BitBake trunk is now GPLv2 only, no mix of
MIT,FreeBSD License is left.
Update GPL headers to point to the correct
address of the FSF
Update the list of authors. Uli Luckas,
Seb Frankengul and Tim Amsell contributed to
the sourcecode as well
|
|
|
|
|
|
|
|
bitbake/lib/bb/__init__.py:
bitbake/lib/bb/shell.py:
bitbake/lib/bb/runqueue.py:
bitbake/lib/bb/msg.py:
bitbake/MANIFEST:
bitbake/bin/bitbake:
Major rewrite and modularisation of the dependecy code. The code in bin/bitbake
is replaced by the taskdata and runqueue modules. The code is designed to support
multiple threads (although the initial threading algothirm is simplistic). The
new code is aimed to be maintainable and debuggable (once msy.py is finished).
|
|
|
|
|
Richard Purdie
Chris Larson
Chris Larson
Chris Larson
Richard Purdie
Holger Hans Peter Freyther
Marcin Juszkiewicz