Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "Alexander Kanavin" <alex.kanavin@gmail.com>,
	"Quentin Schulz" <quentin.schulz@cherry.de>,
	"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] dev-manual: add command to force a recipe re-compile
Date: Wed, 10 Jun 2026 15:13:13 +0200	[thread overview]
Message-ID: <DJ5E9EXAKEDO.K4UR4XPB3FS@bootlin.com> (raw)
In-Reply-To: <c6a477d5-10a4-5775-7031-33b2b10a3a71@crashcourse.ca>

On Wed Jun 10, 2026 at 2:59 PM CEST, Robert P. J. Day wrote:
> On Wed, 10 Jun 2026, Antonin Godard via lists.yoctoproject.org wrote:
>
>> On Wed Jun 10, 2026 at 11:51 AM CEST, Robert P. J. Day wrote:
>> > On Wed, 10 Jun 2026, Alexander Kanavin wrote:
>> >
>> >> On Wed, 10 Jun 2026 at 11:24, Quentin Schulz <quentin.schulz@cherry.de> wrote:
>> >> > Do not modify a recipe's unpacked source code, it's the best way to have
>> >> > your changes lost. There are non-negligible chances that it'll end up
>> >> > being deleted and unpacked again (e.g. because the cache is outdated via
>> >> > its dependencies or the recipe parsing resulted in a rebuild of the recipe).
>> >> >
>> >> > Using -f also taints the build and you need to clean the sstate-cache
>> >> > for this recipe to recover from it last time I checked, which is
>> >> > something we don't like recommending to people (if you need to clean the
>> >> > sstate-cache, either something's wrong with your recipe or there's a bug
>> >> > we need to fix), so I don't think documenting this enormous footgun is a
>> >> > good thing.
>> >>
>> >> I agree, I'd rather not mention it at all, and point people directly to devtool.
>> >
>> >   ok, i'll add that but, as i just mentioned, it's there in the quilt
>> > section as well.
>>
>> I think keeping the Quilt document is fine and in this case the
>> command makes sense, however, it would be nice to inform users in
>> this document that devtool is available and friendlier. Could you
>> add this note?
>
>   there is alreaady a note at the top of the quilt section
> recommending devtool.

Ah perfect then.

Antonin


  reply	other threads:[~2026-06-10 13:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 19:20 [PATCH] dev-manual: add command to force a recipe re-compile Robert P. J. Day
2026-06-10  7:27 ` [docs] " Alexander Kanavin
2026-06-10  8:36   ` Robert P. J. Day
2026-06-10  9:24     ` Quentin Schulz
2026-06-10  9:26       ` Alexander Kanavin
2026-06-10  9:51         ` Robert P. J. Day
2026-06-10 12:54           ` Antonin Godard
2026-06-10 12:59             ` Robert P. J. Day
2026-06-10 13:13               ` Antonin Godard [this message]
2026-06-10  9:50       ` Robert P. J. Day

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=DJ5E9EXAKEDO.K4UR4XPB3FS@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=rpjday@crashcourse.ca \
    /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