From: Henning Schild <henning.schild@siemens.com>
To: "Moessbauer, Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan (T RDA IOT)" <jan.kiszka@siemens.com>,
"Schmidt,
Adriaan (T RDA IOT SES-DE)" <adriaan.schmidt@siemens.com>
Subject: Re: Lightning talk about ISAR
Date: Fri, 26 Nov 2021 21:20:48 +0100 [thread overview]
Message-ID: <20211126212048.071fdcb3@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20211125211705.1e3723fc@md1za8fc.ad001.siemens.net>
We also have a bunch of commits for reproducible builds, i am afraid
still (upcoming).
I carry them as "henning/staging10"
https://github.com/henning-schild-work/isar/tree/henning/staging10
Yes ... two digit open "MRs" ...
Might be worth mentioning because "reproducible builds" will be a
keynote talk on that event.
OT
i stopped all rebasing and pinging because we need that sstate to speed
up and get all those open MRs merged. Some of them introduce tests and
i decided to hold them back after avocado. Will be happy to re-send
once sstate is in and we gain some much needed speed.
Henning
Am Thu, 25 Nov 2021 21:17:05 +0100
schrieb Henning Schild <henning.schild@siemens.com>:
> Am Thu, 25 Nov 2021 11:42:00 +0100
> schrieb "Moessbauer, Felix (T RDA IOT SES-DE)"
> <felix.moessbauer@siemens.com>:
>
> > Dear subscribers,
> >
> >
> >
> > we plan to give a lightning talk about recent changes in ISAR at the
> > “Linux Community Event” conference (Siemens internal).
>
> lightning talk means we got a 15min slot, it seems too much content to
> me, or maybe we get a longer slot for that talk
>
> > The talk should give an overview about major changes and features,
> > added to ISAR since the last year.
>
> Besides features we see more and more adoption and users being pretty
> happy to build with ISAR.
> That includes Siemens internal communication and what we saw coming
> from Intel and others. Users who are happy and do not even show up on
> this list. Might be worth putting on a slide.
>
> >
> >
> > Below you will find a list of topics we plan to present.
> >
> > Are there any further topics which we should cover?
> >
> >
> >
> > - distro support
> >
> > - added debian bullseye
> >
> > - added ubuntu (focal)
> >
> > - target support
> >
> > - added sample RISC-V target
> >
> > - image formats
> >
> > - added OVA (VMWare) image type
> >
> > - added CPIO image type (initramfs like filesystem)
> >
> > - generate OCI (container) filesystem
> >
> > - Performance optimizations
> >
> > - SState
> >
> > - CCache (Upcoming)
>
>
> We have the sbuild/schroot story (upcoming). I did not yet try it but
> guess it will be a performance topic (because of less serialization)
> and a quality topic because of "Build-Depends".
>
> Seeing the so far very positive adoption i would conclude that
> "performance" it the #1 in all that has happened. With all the other
> topics being "we care to improve and cater".
>
> regards,
> Henning
>
> >
> >
> > Minor changes:
> >
> > - Install prebuild DPKD packages from third party sources
> >
> > - Support for apt sources in "Absolute Component Format"
> >
> > - Package building
> >
> > - DEBIAN_BUILD_DEPENDS as BB parameter
> >
> > - DEBIAN_CONFLICTS as BB parameter
> >
> > - git as default patchtool
> >
> > - Warn if FS has Y2038 issue
> >
> > - Changes to ISAR_RELEASE_CMD (upcoming)
> >
> > Best regards,
> > Felix
> >
>
next prev parent reply other threads:[~2021-11-26 20:20 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 [this message]
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
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=20211126212048.071fdcb3@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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