public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
Subject: Re: [PATCH 0/4] Allow better control over container tags
Date: Wed, 28 Jul 2021 17:23:47 +0200	[thread overview]
Message-ID: <20210728172347.43bf0fe9@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210728152210.7089-1-henning.schild@siemens.com>

This can also be found here:
 https://github.com/henning-schild-work/isar/tree/henning/staging

And so that CI picks it up here:
 https://github.com/henning-schild-work/isar/tree/henning/ilbers-ci

Henning

Am Wed, 28 Jul 2021 17:22:06 +0200
schrieb Henning Schild <henning.schild@siemens.com>:

> A container tags consists of "name:tag" and both have been kind of
> hardcoded so far. "tag" was always "latest" which is not proper
> versioning. And "name" has always been "isar-DISTRO-ARCH" which is
> also not proper because the name should probably describe the content
> and not so much the build system. Plus that name means guaranteed
> collision if you build two containers with isar based on the same
> disto and arch.
> 
> p3 is kind of interface breaking, i may have forgotten some docs and
> stuff
> 
> Henning Schild (4):
>   classes: make sure container extension can run multiple times
>   classes: simplify tag handling in container class
>   classes: allow more control over container image name and tag
>   classes: fix comment in container-img class
> 
>  meta/classes/container-img.bbclass            |  6 ++---
>  .../classes/image-container-extension.bbclass | 25
> ++++++++++--------- meta/classes/image-sdk-extension.bbclass      |
> 2 +- 3 files changed, 16 insertions(+), 17 deletions(-)
> 


  parent reply	other threads:[~2021-07-28 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 15:22 Henning Schild
2021-07-28 15:22 ` [PATCH 1/4] classes: make sure container extension can run multiple times Henning Schild
2021-07-29  8:29   ` Silvano Cirujano Cuesta
2021-07-28 15:22 ` [PATCH 2/4] classes: simplify tag handling in container class Henning Schild
2021-07-29  8:49   ` Silvano Cirujano Cuesta
2021-07-28 15:22 ` [PATCH 3/4] classes: allow more control over container image name and tag Henning Schild
2021-07-29 12:50   ` Silvano Cirujano Cuesta
2021-07-29 13:05     ` Henning Schild
2021-07-29 13:13       ` Silvano Cirujano Cuesta
2021-07-28 15:22 ` [PATCH 4/4] classes: fix comment in container-img class Henning Schild
2021-07-29 12:52   ` Silvano Cirujano Cuesta
2021-07-28 15:23 ` Henning Schild [this message]
2021-07-29 12:58 ` [PATCH 0/4] Allow better control over container tags Silvano Cirujano Cuesta

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=20210728172347.43bf0fe9@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --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