public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH] imagetypes: update recipe API changelog
Date: Wed, 4 May 2022 12:42:23 +0000	[thread overview]
Message-ID: <AS4PR10MB5318ED3F1E82BB7A6122AAF9EDC39@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <9e2dc0a33d51c0e3480b6a3effd04ab038bf6648.camel@siemens.com>

Bezdeka, Florian (T CED SES-DE), 4. Mai 2022 14:32:
> On Wed, 2022-05-04 at 14:16 +0200, Adriaan Schmidt wrote:
> > +
> > +Changes when using the built-in types:
> > +  * Image recipes no longer inherit their image type class.
> > +  * Names of image types, as defined using IMAGE_FSTYPES, no longer have
> the
> > +    suffix `-img`, i.e., `wic-img` becomes `wic`, `ext4-img` becomes
> `ext4`,
> > +    and so on.
> > +  * Image types defined in IMAGE_FSTYPES can be suffixed with conversions.
> > +    To get a compressed image, set IMAGE_FSTYPES to `wic.xz`, `ext4.gz`,
> etc.
> > +    That also means that the type of the previous `targz-img` is not
> `tar.gz`.
>                                                                     ^^
>                                                                     now?

Yes! (somewhat unfortunate typo that inverts the meaning...)

> > +  * Container types (previously CONTAINER_IMAGE_FORMATS) are now
> > +    first class image types (oci, oci-archive, docker-archive,
> > +    docker-daemon, containers-storage)
> > +  * The VM image now has type `ova` (instead of `vm-img`)


      reply	other threads:[~2022-05-04 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 12:16 Adriaan Schmidt
2022-05-04 12:31 ` Bezdeka, Florian
2022-05-04 12:42   ` Schmidt, Adriaan [this message]

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=AS4PR10MB5318ED3F1E82BB7A6122AAF9EDC39@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM \
    --to=adriaan.schmidt@siemens.com \
    --cc=florian.bezdeka@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