From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
"Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [ANNOUNCE] Upcoming ISAR release
Date: Mon, 18 Feb 2019 21:09:26 +0100 [thread overview]
Message-ID: <3312e43d-bac5-f8c0-76ad-8b71c6ebc0d8@siemens.com> (raw)
In-Reply-To: <206fc335-0158-6288-a23a-e34852c12784@siemens.com>
On 18.02.19 12:52, [ext] Claudius Heine wrote:
>>>
>>> - Remove jessie support
>>
>> That's a point which I don't understand - yes, we don't support jessie as a
>> host system, but why don't continue to support jessie based targets if this
>> doesn't require big efforts?
>
> Well IMO it does require effort as shown with the unavailable `-d` parameter in
> mkfs.ext4. For image creation not the build machine tools should be used but
> those of the host (or what you call target), which should then be >=stretch. The
> image creation tools might have patches applied to them.
Jessie might be nice from testing perspective, but only when it's not making
life too hard for moving on. Practically, it plays no role in the field, simply
because everyone started on Stretch as Isar was not usable at the time jessie
was the latest version.
>
>> Industrial programming is very conservative in this point (that's why all
>> these https://www.cip-project.org/ serve for).
>
> That has nothing to do with this. linux-cip is a project to support kernel
> versions for ~25 years. AFAIK nobody does that for the userspace.
Not quite: Kernel and a set of Debian core packages (we are still shaping the
latter set) will be maintained for 10 (ten) years. There will soon be an
official Isar layer encoding that package set (it's currently only in
https://gitlab.com/cip-playground/isar-cip-core).
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-18 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 9:01 Maxim Yu. Osipov
2019-02-18 9:58 ` Claudius Heine
2019-02-18 10:29 ` Maxim Yu. Osipov
2019-02-18 11:52 ` Claudius Heine
2019-02-18 17:16 ` Henning Schild
2019-02-18 20:09 ` Jan Kiszka [this message]
2019-02-18 10:07 ` Henning Schild
2019-02-18 10:25 ` Jan Kiszka
2019-02-26 14:23 ` cedric_hombourger
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=3312e43d-bac5-f8c0-76ad-8b71c6ebc0d8@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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