From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta-isar: hello: Use <orig-version> in CHANGELOG_V
Date: Fri, 8 May 2020 08:13:21 +0200 [thread overview]
Message-ID: <20200508061321.htleuouxxfp2mv4x@yssyq.m.ilbers.de> (raw)
In-Reply-To: <230091c6-9906-9dc5-77cd-66f086b6b99a@siemens.com>
On Fri, May 08, 2020 at 08:05:33AM +0200, Jan Kiszka wrote:
> > This is a very typical Debian vs. bitbake problem which falls into the 20% that
> > bitbake doesn't solve nicely. Another example is static DEPENDS of bitbake vs.
> > Debian's dynamic Depends that become known only after fetching. Besides hacking
> > the relevant places like do_apt_fetch, these currently tend to require
> > non-intuitive, hard-to-debug stuff like S="${@...}" or anonymous functions. I
>
> Even that Python inlining won't help because it runs too early, during
> parsing, as well and we need that after some tasks have been completed,
> namely the apt-src fetching and unpacking.
IIRC, we had a PoC that did early pre-fetching, but that goes then completely
outside of the bitbake pipeline, which is a hack that would eventually bite,
given enough packages to build. So our next step was to look at managing the
pipeline dynamically, which would be a major change.
With kind regards,
Baurzhan.
prev parent reply other threads:[~2020-05-08 6:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:29 Jan Kiszka
2020-04-28 16:00 ` Henning Schild
2020-04-28 16:01 ` Jan Kiszka
2020-04-29 5:54 ` Henning Schild
2020-04-29 6:10 ` Jan Kiszka
2020-04-29 6:27 ` Henning Schild
2020-04-29 6:37 ` Henning Schild
2020-04-29 6:51 ` Henning Schild
2020-06-05 17:46 ` Henning Schild
2020-06-05 17:55 ` Jan Kiszka
2020-06-06 8:10 ` Henning Schild
2020-06-06 8:37 ` Baurzhan Ismagulov
2020-06-08 7:59 ` Jan Kiszka
2020-05-07 20:09 ` Baurzhan Ismagulov
2020-05-08 6:05 ` Jan Kiszka
2020-05-08 6:13 ` Baurzhan Ismagulov [this message]
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=20200508061321.htleuouxxfp2mv4x@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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