Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Aleksandar Nikolic" <aleksandar.nikolic010@gmail.com>
To: "Dmitry Baryshkov" <dbaryshkov@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Yocto Binary Distro
Date: Tue, 08 Oct 2024 01:30:47 -0700	[thread overview]
Message-ID: <11278.1728376247903375011@lists.yoctoproject.org> (raw)
In-Reply-To: <CALT56yOVpmvaS+oWDG1oJeOLOW2NbLq6TwCGwisFqh=4c95h8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On Tue, Oct 8, 2024 at 01:25 AM, Dmitry Baryshkov wrote:

> 
> Consider using shared SSTATE, it saves you from all the rebuilds,
> while keeping Yocto internals intact and sane.

We are using sstate cache, but if I am not mistaken it can happen that even though a package is in the sstate cache, there's a cache miss and the package gets rebuilt - and this is exactly what some coworkers would like to avoid, cause it means a different binary is on the target than the one previously built and tested. That's why I posted another question here (maybe 2 weeks ago) if there's a way to force Yocto to only use sstate-cache and fail if a package needs to be rebuilt or to print a list of packages which were built from source. But there's no an "easy" way to do it.

Aleksandar

> 
> --
> With best wishes
> Dmitry

[-- Attachment #2: Type: text/html, Size: 938 bytes --]

  reply	other threads:[~2024-10-08  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07  5:03 Yocto Binary Distro Aleksandar Nikolic
2024-10-07 11:31 ` [yocto] " Alexander Kanavin
2024-10-07 14:43   ` Aleksandar Nikolic
2024-10-07 19:07   ` Dmitry Baryshkov
2024-10-07 19:27     ` Alexander Kanavin
2024-10-07 19:29       ` Dmitry Baryshkov
2024-10-07 20:34         ` Aleksandar Nikolic
2024-10-07 23:25           ` Dmitry Baryshkov
2024-10-08  8:30             ` Aleksandar Nikolic [this message]
2024-10-08  8:53               ` Mikko Rapeli
2024-10-08 12:09                 ` Aleksandar Nikolic
2024-10-08 12:16                   ` Mikko Rapeli

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=11278.1728376247903375011@lists.yoctoproject.org \
    --to=aleksandar.nikolic010@gmail.com \
    --cc=dbaryshkov@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /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