public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [RFC 0/4] PoC for isar-apt repo reusing
Date: Fri, 3 Sep 2021 10:43:57 +0200	[thread overview]
Message-ID: <20210903084357.GG28547@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20210902131145.3d871949@md1za8fc.ad001.siemens.net>

On Thu, Sep 02, 2021 at 01:11:45PM +0200, Henning Schild wrote:
> i did not look into the details yet. Just wanted to let you know that
> we do have a prototype implementation of using sstate caching. That
> allows caching anything, not just isar-apt.

Looking forward to the sstate-cache patches. I think both are useful. Sstate
caching is about speeding up package building, isar-apt is about Debian
workflows.

Also, Isar will eventually have to track and distinguish between base-apt and
isar-apt. This is needed for correctness if isar-apt provides Build-Depends for
other self-built packages (linux-headers, openssl-dev, etc.).

On a related note, we've also tested ccache and would hopefully share the
patches soon -- it would speed up building when packages do change.

With kind regards,
Baurzhan.

  reply	other threads:[~2021-09-03  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02  9:58 Uladzimir Bely
2021-09-02  9:58 ` [RFC 1/4] meta-isar: Fix do_dpkg_build override for prebuild-deb recipe Uladzimir Bely
2021-09-02  9:58 ` [RFC 2/4] isar-apt: PoC of reusing isar-apt repo Uladzimir Bely
2021-09-02  9:58 ` [RFC 3/4] ci: Test for isar-apt reuse Uladzimir Bely
2021-09-02  9:58 ` [RFC 4/4] doc: Add section for isar-apt reuse functionality Uladzimir Bely
2021-09-02 11:11 ` [RFC 0/4] PoC for isar-apt repo reusing Henning Schild
2021-09-03  8:43   ` Baurzhan Ismagulov [this message]
2021-09-03  5:52 ` Jan Kiszka
2021-09-03  8:18   ` Uladzimir Bely

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=20210903084357.GG28547@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --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