All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] dev-manual: correct statement that source is always tarballs
@ 2025-06-22 14:50 Robert P. J. Day
  2025-06-23 14:19 ` [docs] " Quentin Schulz
  2025-06-24  7:47 ` Antonin Godard
  0 siblings, 2 replies; 3+ messages in thread
From: Robert P. J. Day @ 2025-06-22 14:50 UTC (permalink / raw)
  To: YP docs mailing list


It's misleading to suggest that source is always fetched as tarballs.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

diff --git a/documentation/dev-manual/efficiently-fetching-sources.rst b/documentation/dev-manual/efficiently-fetching-sources.rst
index a15f0a92c..2f8a68e20 100644
--- a/documentation/dev-manual/efficiently-fetching-sources.rst
+++ b/documentation/dev-manual/efficiently-fetching-sources.rst
@@ -6,7 +6,7 @@ Efficiently Fetching Source Files During a Build
 The OpenEmbedded build system works with source files located through
 the :term:`SRC_URI` variable. When
 you build something using BitBake, a big part of the operation is
-locating and downloading all the source tarballs. For images,
+locating and downloading all of the source. For images,
 downloading all the source for various packages can take a significant
 amount of time.



^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [docs] [PATCH] dev-manual: correct statement that source is always tarballs
  2025-06-22 14:50 [PATCH] dev-manual: correct statement that source is always tarballs Robert P. J. Day
@ 2025-06-23 14:19 ` Quentin Schulz
  2025-06-24  7:47 ` Antonin Godard
  1 sibling, 0 replies; 3+ messages in thread
From: Quentin Schulz @ 2025-06-23 14:19 UTC (permalink / raw)
  To: rpjday, YP docs mailing list

Hi Robert,

On 6/22/25 4:50 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
> 
> It's misleading to suggest that source is always fetched as tarballs.
> 

Seems like a reasonable change to me,

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [docs] [PATCH] dev-manual: correct statement that source is always tarballs
  2025-06-22 14:50 [PATCH] dev-manual: correct statement that source is always tarballs Robert P. J. Day
  2025-06-23 14:19 ` [docs] " Quentin Schulz
@ 2025-06-24  7:47 ` Antonin Godard
  1 sibling, 0 replies; 3+ messages in thread
From: Antonin Godard @ 2025-06-24  7:47 UTC (permalink / raw)
  To: Robert P. J. Day, YP docs mailing list

On Sun Jun 22, 2025 at 4:50 PM CEST, Robert P. J. Day wrote:
>
> It's misleading to suggest that source is always fetched as tarballs.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/documentation/dev-manual/efficiently-fetching-sources.rst b/documentation/dev-manual/efficiently-fetching-sources.rst
> index a15f0a92c..2f8a68e20 100644
> --- a/documentation/dev-manual/efficiently-fetching-sources.rst
> +++ b/documentation/dev-manual/efficiently-fetching-sources.rst
> @@ -6,7 +6,7 @@ Efficiently Fetching Source Files During a Build
>  The OpenEmbedded build system works with source files located through
>  the :term:`SRC_URI` variable. When
>  you build something using BitBake, a big part of the operation is
> -locating and downloading all the source tarballs. For images,
> +locating and downloading all of the source. For images,

This is also present slightly below, in the same document. Can you replace that
occurence too?

Also I would suggest "all of the source code" instead of "all of the source".

Antonin

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-06-24  7:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-22 14:50 [PATCH] dev-manual: correct statement that source is always tarballs Robert P. J. Day
2025-06-23 14:19 ` [docs] " Quentin Schulz
2025-06-24  7:47 ` Antonin Godard

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.