[RFC 0/5] Debian dependencies investigation

[Anton Mikanovich <amikan@ilbers.de>]

Isar do not jet use Build-Depends field from control files to call
recipes building. DEPENDS field should be used instead in every single
case.

We can use additional source package management to fix that: build
source packages at first stage, obtain dependencies on second and build
final target on third.

It is not something to be used as-is, but just proof of concept to show
possible way for implementation. Proposed logic can't be implemented by
bitbake currently because all the dependencies are calculated before the
build, so we should try to work with upstream to find integration
possibilities.

Anton Mikanovich (5):
  dpkg-base: Cover do_apt_unpack task by lock
  meta: Implement two stage build
  libhello: Declare provided packages
  hello-isar: Remove duplicated dependency
  isar: Add external builder

 isar_builder.py                               | 142 ++++++++++++++++++
 .../recipes-app/hello-isar/hello-isar.bb      |   4 -
 meta-isar/recipes-app/libhello/libhello.bb    |   2 +
 meta/classes/dpkg-base.bbclass                |  36 ++++-
 meta/classes/dpkg-gbp.bbclass                 |   6 +-
 meta/classes/dpkg-prebuilt.bbclass            |   7 +
 meta/classes/dpkg.bbclass                     |  21 ++-
 meta/classes/rootfs.bbclass                   |   2 +
 .../buildchroot/buildchroot.inc               |   2 +
 .../buildchroot/files/build-source.sh         |  16 ++
 .../buildchroot/files/build.sh                |   2 +-
 11 files changed, 222 insertions(+), 18 deletions(-)
 create mode 100755 isar_builder.py
 create mode 100644 meta/recipes-devtools/buildchroot/files/build-source.sh

-- 
2.25.1