Re: [PATCH 0/4 v5] Isar apt deployment

[Christian Storm <christian.storm@siemens.com>]

> [...]
> I would suggest the following changes:
> - create one task in dpkg-base.bbclass that does the following
>  - config and init reprepro if no other recipe did that before
>  - add package
>  - use bitkages task[lockfiles] to deal with races between recipes,
>    put distro into lockfile-name so we have one lock per distro 
> - drop do_populate
> - call the new task instead of, or in do_deploy_deb

This would be quite useful to source builds with dependencies: Consider
three source built packages A, B, and C. A and B are -dev packages to be
built prior to C. Both may have dependencies satisfiable from the
Debian mirrors. Then, when building C, A and B have to be installed as
build-time dependencies into the buildchroot prior to building C. For
this, the DEPENDS= may be used in the recipe of C to install A and B
just like with any other dependencies coming from the Debian mirrors
as they're in the reprepro repository that must be made accessible in the
buildchroot. For this to work, there's an apt get update needed to
refresh the "view" of the reprepro in the buildchroot after package
addition. This update should be restricted to the reprepro and not
update from the Debian mirrors.

Currently, installing A and B into the buildchroot may be done via
via dpkg -i from DEPLOY_DEB_DIR/{A,B} but this doesn't handle
dependencies. Having A and B in the reprepro repository, and this
reprepro repository being available to the buildchroot, an apt-get
install {A,B} derived from DEPENDS= would work.



Kind regards,
   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany