public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Moessbauer,
	Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schild, Henning (T RDA IOT SES-DE)" <henning.schild@siemens.com>,
	"Schmidt,
	Adriaan (T RDA IOT SES-DE)" <adriaan.schmidt@siemens.com>
Subject: Re: Lightning talk about ISAR
Date: Thu, 25 Nov 2021 17:26:07 +0100	[thread overview]
Message-ID: <756eb9e7-ab01-e48e-2021-c906ef37c74e@siemens.com> (raw)
In-Reply-To: <AM9PR10MB4869D829C16854173F494A8589629@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>

On 25.11.21 11:42, Moessbauer, Felix (T RDA IOT SES-DE) wrote:
> Dear subscribers,
> 

Dear sender: please no HTML on public mailing lists.

> 
> we plan to give a lightning talk about recent changes in ISAR at the
> “Linux Community Event” conference (Siemens internal).
> The talk should give an overview about major changes and features, added
> to ISAR since the last year.
> 
> Below you will find a list of topics we plan to present.
> Are there any further topics which we should cover?

Which timeframe would you cover? Roughly last 2 years?

> 
> - 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

+ containerized SDK

> - Performance optimizations
>   - SState
>   - CCache (Upcoming)

sstate is upcoming, ccache is in.

> 
> 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)

- deb-src caching
- deb_debianize received quite a few detail improvements
- package build for 32-bit compat archs
- TF-A and OP-TEE packaging support
- new testsuite (avocado based) -> relevant for contributors

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-11-25 16:26 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 [this message]
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

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=756eb9e7-ab01-e48e-2021-c906ef37c74e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@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