All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <corentin.guillevic@smile.fr>, <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH v5 4/4] doc/bitbake-setup: document "uri" property
Date: Tue, 23 Dec 2025 11:59:10 +0100	[thread overview]
Message-ID: <DF5JKPLOIHB1.3B4RJC8E90CG@bootlin.com> (raw)
In-Reply-To: <20251223101757.1057188-4-corentin.guillevic@smile.fr>

Hi,

On Tue Dec 23, 2025 at 11:17 AM CET, Corentin Guillevic via lists.openembedded.org wrote:
> The property 'uri' is a simplification of the property 'remotes'. It is
> used to provide only one URI.
>
> Signed-off-by: Corentin Guillevic <corentin.guillevic@smile.fr>
> ---
>  .../bitbake-user-manual-environment-setup.rst        | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst b/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst
> index ec1bdeecd..b3588f27d 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-environment-setup.rst
> @@ -673,11 +673,7 @@ They contain the following sections:
>           "sources": {
>               "bitbake": {
>                   "git-remote": {
> -                     "remotes": {
> -                         "origin": {
> -                             "uri": "https://git.openembedded.org/bitbake"
> -                         }
> -                     },

Can you please port this deleted example under the description of the "remotes"
property?

We still want to show how someone can configure this property. It would be nice
if you could showcase another remote name, so it highlights why this option
could be used instead of the simplified "uri" option.

Something like:

  "git-remote": {
      "remotes": {
          "origin": {
              "uri": "https://git.openembedded.org/bitbake"
          },
          "contrib": {
              "uri": "https://git.openembedded.org/bitbake-contrib"
          }
      },
  }

And then explain how one or the other can be used with bitbake-setup (I have no
clue).

This also makes the "remotes" option optional, so you need to update its
description.

> +                     "uri": "https://git.openembedded.org/bitbake",
>                       "branch": "master",
>                       "rev": "master"
>                   },
> @@ -716,6 +712,12 @@ They contain the following sections:
>        -  ``branch`` (**required**): the Git branch, used to check that the
>           specified ``rev`` is indeed on that branch.
>  
> +      -  ``uri`` (*optional*): a URI that follows the git URI syntax. Can replace the

s/Can/You can/

> +         ``remotes`` structure if only one URI is provided. Despite this, ``uri`` and
> +         ``remotes`` can still be used together.
> +
> +         See https://git-scm.com/docs/git-clone#_git_urls for more information.
> +
>     -  ``local`` (*optional*): specifies a path on local disk that should be symlinked
>        to under ``layers/``. This is useful for local development, where some layer
>        or other component used in a build is managed separately, but should still be

Thanks,
Antonin

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



      reply	other threads:[~2025-12-23 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23 10:17 [PATCH v5 1/4] bitbake-setup: add inline URI Corentin Guillevic
2025-12-23 10:17 ` [PATCH v5 2/4] layers.schema.json: support 'uri' Corentin Guillevic
2025-12-23 10:17 ` [PATCH v5 3/4] bitbake-setup: use URI shortcut for all configurations Corentin Guillevic
2026-01-09 13:41   ` [bitbake-devel] " Alexander Kanavin
2025-12-23 10:17 ` [PATCH v5 4/4] doc/bitbake-setup: document "uri" property Corentin Guillevic
2025-12-23 10:59   ` Antonin Godard [this message]

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=DF5JKPLOIHB1.3B4RJC8E90CG@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=corentin.guillevic@smile.fr \
    /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.