All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] should replicating offline build use "--runonly" or "--runall"?
Date: Tue, 24 Jun 2025 09:57:24 +0200	[thread overview]
Message-ID: <DAULQE8WNN68.2YBA6IQ3BBCO1@bootlin.com> (raw)
In-Reply-To: <92dee52f-385b-9134-1364-c1f6e673b37a@crashcourse.ca>

On Sun Jun 22, 2025 at 4:45 PM CEST, Robert P. J. Day wrote:
> On Sun, 22 Jun 2025, Robert P. J. Day wrote:
>
>>
>>   this section:
>>
>> https://docs.yoctoproject.org/dev-manual/building.html#replicating-a-build-offline
>>
>> advises to fetch the sources with:
>>
>>   $ bitbake target --runonly=fetch
>>
>> for the longest time now, i've used:
>>
>>   $ bitbake target --runall=fetch
>>
>> although i do recall that those behaviours changed once upon a time.
>> so is that still the appropriate command to use? is it worth adding an
>> explanation at that point as to the difference for people who might be
>> curious?
>
>   as a followup, this section:
>
> https://docs.yoctoproject.org/dev-manual/efficiently-fetching-sources.html
>
> refers only to "--runall=fetch". so it seems inconsistent with the
> earlier section. or, at the very least, it has the potential for
> confusion.

Yes, I also --runall should be used. I'd take a patch.

Thanks,
Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-06-24  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <184B5224024A6359.12316@lists.yoctoproject.org>
2025-06-22 14:45 ` [docs] should replicating offline build use "--runonly" or "--runall"? Robert P. J. Day
2025-06-24  7:57   ` Antonin Godard [this message]
2025-06-24 10:02     ` 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=DAULQE8WNN68.2YBA6IQ3BBCO1@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.