public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: docs: technical-overview is outdated (no sbuild, imagetypes)
Date: Mon, 21 Nov 2022 04:07:07 +0000	[thread overview]
Message-ID: <afd69c6ba80275d40c40034706f9546529e629d7.camel@siemens.com> (raw)

Dear ISAR users,

while reading the technical_overview.md documentation [1], I saw that
this is quite outdated. Especially section 3.5 about custom package
building is not correct anymore, as it still describes the behavior
before the integration of sbuild.
If nobody is working on it, I would be willing to rework it once I find
some time.

Also the section 3.7 about image building is no longer correct. Maybe
Adriaan could have a look and describe the imagetypes infrastructure.
Or we simply remove it.

Felix

[1]
https://github.com/ilbers/isar/blob/master/doc/technical_overview.md#35-building-custom-packages

                 reply	other threads:[~2022-11-21  4:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=afd69c6ba80275d40c40034706f9546529e629d7.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=adriaan.schmidt@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