public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: ydirson@free.fr
Cc: isar-users@googlegroups.com
Subject: Re: status of meta-eid ?
Date: Mon, 25 Oct 2021 10:02:02 +0200	[thread overview]
Message-ID: <20211025100202.0da43e3a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <1428583705.1338909396.1635103133648.JavaMail.root@zimbra39-e7>

Am Sun, 24 Oct 2021 21:18:53 +0200 (CEST)
schrieb ydirson@free.fr:

> Hi Baurzhan,
> 
> > sbuild preview is available in [1].  
> 
> Nice!
> 
> > If you are interested, we could share the current state.   
> 
> I still have quite a lot in dig in right now, so don't divert efforts
> :)
> 
> My main focus for now is a bit far from this - I still need to get
> familiar with the current state of things, with in mind the idea of
> possibly using ISAR as a next-gen build system[1] for QubesOS[0] (a
> bit of a personal research project to see if it can help to improve
> the dev workflow there)
> 
> [0] https://qubes-os.org/
> [1]
> https://forum.qubes-os.org/t/ideas-for-next-generation-qubes-builder/6402

Cater as a build system for an OSS project like qubes-os would be cool.
I looked into 1 and it seems qubes-os is currently based on fedora.

Making isar work for that would be possible but not an easy task. It is
already hard to keep all the different flavours/versions of debian
maintained and working. Plus we are building on top of qemu-debootstrap
for native builds of non-host architectures. A very powerful thing that
might be missing some bits in other distros.

In fact Isar is not a lot of code, and most of it is very much debian
specific. The easiest way to go might be switching base distros, which
might bring you "back in time" and on a slower release cycle your might
be used to. And if you carry a lot of your own spec-files, those will
need translation into "debian/" folders.

Also note that Isars main feature is building complete bootable images,
or OTA-update rootfss. For more than just a rootfs, partitioning and
bootloader stuff come into play. It also builds debian package repos
for later offline rebuild or for shipping package-based updates with
apt.
If your main concern is building packages, and maybe package repos ...
it might be too big of a gun (but will work). On the other hand full
bootable image is what you might still need for automated continous
testing in qemu or on real devices.

regards,
Henning

> (sorry for somewhat breaking the thread, I'm apparently not receiving
> answers -- nothing new here from google servers unfortunately)
> 


  reply	other threads:[~2021-10-25  8:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1862287450.1338648081.1635097358493.JavaMail.root@zimbra39-e7>
2021-10-24 17:46 ` ydirson
2021-10-24 17:58   ` Baurzhan Ismagulov
2021-10-24 19:18   ` ydirson
2021-10-25  8:02     ` Henning Schild [this message]
2021-10-25 11:15       ` ydirson
2021-10-25 11:58         ` 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=20211025100202.0da43e3a@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ydirson@free.fr \
    /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