public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
To: <isar-users@googlegroups.com>, <ibr@radix10.net>,
	<silvano.cirujano-cuesta@siemens.com>
Cc: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: [RFC PATCH 0/2] Custom base-files
Date: Sat, 20 Feb 2021 01:27:17 +0530	[thread overview]
Message-ID: <20210219195719.29037-1-Vijaikumar_Kanagarajan@mentor.com> (raw)

This series introduced 2 patchsets.
P1 though could be a separate patchset, is clubbed with this series
since it is needed for P2.

This series removes the postprocessing logic that modifies /etc/os-release
to inject custom data into it. Instead, proposes a custom base-files
based approach to solve the problem.

The basic issue identified with the post-processing approach is that
the information put onto /etc/os-release will be overwritten by the
one provided by the base-files package on reinstall/upgrade.

For a history of this issue and relevant discussions please see [1]

[1]https://groups.google.com/g/isar-users/c/Jr3bTPumH-w 

This might need some entry in user-manual and/or changelog. Will be
added after further testing and in the final version of the patchset.

Vijai Kumar K (2):
  dpkg-base: Handle custom source directory in do_apt_fetch
  recipes-core: Add recipe for base-files

 .../recipes-core/images/isar-image-base.bb    |  2 +
 meta/classes/dpkg-base.bbclass                |  7 ++-
 meta/classes/image-postproc-extension.bbclass | 40 --------------
 meta/classes/image.bbclass                    | 20 -------
 meta/recipes-core/base-files/base-files.bb    |  6 ++
 meta/recipes-core/base-files/base-files.inc   | 55 +++++++++++++++++++
 6 files changed, 69 insertions(+), 61 deletions(-)
 create mode 100644 meta/recipes-core/base-files/base-files.bb
 create mode 100644 meta/recipes-core/base-files/base-files.inc

-- 
2.17.1


             reply	other threads:[~2021-02-19 19:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 19:57 Vijai Kumar K [this message]
2021-02-19 19:57 ` [RFC PATCH 1/2] dpkg-base: Handle custom source directory in do_apt_fetch Vijai Kumar K
2021-02-20  8:07   ` Henning Schild
2021-02-22  7:11     ` vijai kumar
2021-03-03 12:49       ` Henning Schild
2021-03-03 13:49         ` Kanagarajan, Vijaikumar
2021-03-03 14:53           ` Henning Schild
2021-02-19 19:57 ` [RFC PATCH 2/2] recipes-core: Add recipe for base-files Vijai Kumar K
2021-02-20  8:28   ` Henning Schild
2021-02-23  8:38     ` vijai kumar
2021-02-24 12:12       ` Henning Schild
2021-02-25  3:57         ` vijai kumar
2021-02-25  5:08           ` vijaikumar....@gmail.com
2021-02-25  8:20             ` Jan Kiszka
2021-02-25  8:40               ` Jan Kiszka
2021-02-25  9:06               ` vijaikumar....@gmail.com
2021-02-25 16:32                 ` Henning Schild
2021-03-01  5:07                   ` vijaikumar....@gmail.com
2021-03-01  7:35                     ` Henning Schild
2021-03-01  8:04                       ` vijaikumar....@gmail.com
2021-02-25  8:10           ` Henning Schild
2021-02-25  8:26             ` vijaikumar....@gmail.com
2021-02-22 12:39   ` Anton Mikanovich
2021-02-23  8:41     ` vijaikumar....@gmail.com
2021-02-24  9:20       ` vijaikumar....@gmail.com
2021-02-24  9:21         ` Jan Kiszka
2021-02-24 11:40           ` vijaikumar....@gmail.com
2021-02-24 11:54             ` Henning Schild

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=20210219195719.29037-1-Vijaikumar_Kanagarajan@mentor.com \
    --to=vijaikumar_kanagarajan@mentor.com \
    --cc=ibr@radix10.net \
    --cc=isar-users@googlegroups.com \
    --cc=silvano.cirujano-cuesta@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