From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: Baurzhan Ismagulov <ibr@radix50.net>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: Lightning talk about ISAR
Date: Tue, 14 Dec 2021 13:15:09 +0000 [thread overview]
Message-ID: <AS4PR10MB5318BD3335498636031BFCE9ED759@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20211210113610.GM22100@yssyq.m.ilbers.de>
Baurzhan Ismagulov, 10. Dezember 2021 12:36:
> On Fri, Dec 10, 2021 at 12:23:32PM +0100, Jan Kiszka wrote:
> > > Now that avocado and sstate cache is in, if any other patches have
> priority,
> > > please give us a hint.
> >
> > IMHO: Stabilization patches so that 0.8-rc1 can be tagged and then 0.8.
> > After that, we should look into sbuild and other refactorings that are
> > pending.
>
> Right, good point. We've already started checking what needs to be done and
> will post our suggestions.
I still have some follow-ups on the sstate-cache feature:
- Test case that was in the original patch series. This builds on a testsuite
refactoring currently in discussion. Once that is settled I can rebase and
resubmit.
- Documentation: I don't have it yet, but will propose something.
And on sstate-cache, but not quite ready:
- Maintenance script for analysis and cleanup of caches, which we're using
in CI in our downstream project. IT supports persistent/shared caches
on filesystems, HTTP (webdav) servers, and S3 buckets.
Still work in progress, but could be a valuable utility for Isar.
Other work in progress to look forward to, which should then come after this release:
- Refactoring of the (un)mounting logic (was already on the list, mostly works,
but finalizing/testing will be some more effort, and will probably have
collisions with other work like sbuilder (?))
- Extending image types (IMAGE_FSTYPES) to support OE-style type dependencies
and image conversions (not yet on the list). This could greatly improve the
image building/combining experience, but will of course break some interfaces
(esp. in downstream layers that have their own image types). Will try to
post a preview soon.
Adriaan
prev parent reply other threads:[~2021-12-14 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 10:42 Moessbauer, Felix
2021-11-25 16:26 ` Jan Kiszka
2021-11-25 20:17 ` Henning Schild
2021-11-26 20:20 ` Henning Schild
2021-12-09 22:02 ` Henning Schild
2021-12-10 10:56 ` Baurzhan Ismagulov
2021-12-10 11:06 ` Moessbauer, Felix
2021-12-10 11:23 ` Jan Kiszka
2021-12-10 11:36 ` Baurzhan Ismagulov
2021-12-13 21:17 ` Henning Schild
2021-12-15 8:49 ` Baurzhan Ismagulov
2021-12-14 13:15 ` Schmidt, Adriaan [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=AS4PR10MB5318BD3335498636031BFCE9ED759@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
--to=adriaan.schmidt@siemens.com \
--cc=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