From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Christian Storm" <christian.storm@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks
Date: Mon, 11 Dec 2017 12:32:10 +0100 [thread overview]
Message-ID: <20171211123210.5e5c08d4@md1em3qc> (raw)
In-Reply-To: <20171208075806.dxvaf7harsupg7co@MD1KR9XC.ww002.siemens.net>
Am Fri, 8 Dec 2017 08:58:06 +0100
schrieb "[ext] Christian Storm" <christian.storm@siemens.com>:
> > 2. 'do_cleanup': This task is executed after all the packages are
> > deployed. Some notes:
> > - This task also should not have stamp.
> > - This task depends from the recipes listed in IMAGE_INSTALL.
>
> This breaks build dependencies when building two packages from source
> (same example I've given in other posts as well):
These kind of deps are a known missing feature in Isar. Nothing can
break a missing feature.
> Consider A-dev required by B, both to be built from source. B cannot
> install the A-dev.deb since B depending on A-dev's deploy_deb() and
> installing it the ugly way via dpkg -i (as no other option is
> currently available in Isar) puts B as late in the task order so that
> it's git repo is not mounted anymore. Failure.
I think that is what your local hack is based on?
Henning
> If A-dev installs it's produced .deb as last step in its
> dpkg_runbuild(), which is also ugly, then there's a potential race in
> dpkg. Failure.
>
>
> Christian
>
next prev parent reply other threads:[~2017-12-11 11:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 10:25 [PATCH 0/4 v2] Buildchroot prepare/cleanup Alexander Smirnov
2017-11-23 10:25 ` [PATCH 1/4 v2] dpkg-base: Fix buildchroot dependancy Alexander Smirnov
2017-11-23 10:25 ` [PATCH 2/4 v2] image: Add do_rootfs template to image class Alexander Smirnov
2017-11-23 10:25 ` [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks Alexander Smirnov
2017-11-24 14:55 ` Henning Schild
2017-11-24 15:48 ` Alexander Smirnov
2017-11-24 16:34 ` Henning Schild
2017-11-24 16:51 ` Alexander Smirnov
2017-11-27 7:56 ` Henning Schild
2017-11-27 8:15 ` Alexander Smirnov
2017-12-08 7:58 ` Christian Storm
2017-12-11 9:23 ` Alexander Smirnov
2017-12-11 12:16 ` Henning Schild
2017-12-11 13:37 ` Storm, Christian (CT RDA ITP SES-DE)
2017-12-11 14:12 ` Alexander Smirnov
2017-12-11 15:14 ` Christian Storm
2017-12-12 7:39 ` Alexander Smirnov
2017-12-12 8:01 ` Christian Storm
2017-12-12 8:21 ` Alexander Smirnov
2017-12-11 11:32 ` Henning Schild [this message]
2017-12-11 18:29 ` Henning Schild
2017-12-11 19:56 ` Alexander Smirnov
2017-12-12 8:04 ` Christian Storm
2017-12-12 12:05 ` Henning Schild
2017-12-13 5:43 ` Jan Kiszka
2017-12-11 18:32 ` Henning Schild
2017-11-23 10:25 ` [PATCH 4/4 v2] dpkg-base: Update git alternates Alexander Smirnov
2017-11-24 14:57 ` Henning Schild
2017-11-24 15:12 ` Alexander Smirnov
2017-11-27 7:44 ` Henning Schild
2017-11-27 8:03 ` Alexander Smirnov
2017-11-27 15:42 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171211123210.5e5c08d4@md1em3qc \
--to=henning.schild@siemens.com \
--cc=christian.storm@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox