All of lore.kernel.org
 help / color / mirror / Atom feed
From: talhacali@gmail.com
To: yocto@lists.yoctoproject.org
Subject: Re: create-layers-setup Yaml support #bitbake
Date: Wed, 12 Apr 2023 04:12:51 -0700	[thread overview]
Message-ID: <10320.1681297971251679769@lists.yoctoproject.org> (raw)
In-Reply-To: <CANNYZj9q3zBCguBussvczdj=CuuEqY4zvvOEw2jO-kPrHXq13g@mail.gmail.com>

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

Renovate normally doesn't require to make changes in other files.
It supports many package files, and detects them automatically.
It parses them, and finds the dependencies without needing any change.
But, for package files which is not supported by Renovate, a regular expression
is needed inside the file to let Renovate know where to look while parsing the file.
As far as I know, there is no other way than adding a new line to the file.

We are also using Renovate the same way with bb files as well.

We have got a lot of projects, and potential projects that have several different
dependencies. They are hosted in different repositories, and the idea is to update
their dependencies (or not it depends on the project) regularly, and do it automatically.
Like I said, with the package files that Renovate supports such as npm, Dockerfiles, etc. it is easy to do,
but for our case we need to modify the json file with an added comment. For this reason, Yaml files are
an ideal solution for us.

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

  reply	other threads:[~2023-04-12 11:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 13:01 create-layers-setup Yaml support #bitbake talhacali
2023-04-11 14:01 ` [yocto] " Alexander Kanavin
2023-04-11 14:31   ` talhacali
2023-04-11 14:47     ` [yocto] " Alexander Kanavin
2023-04-11 14:49       ` Alexander Kanavin
2023-04-12 11:12         ` talhacali [this message]
2023-04-12 11:34           ` Alexander Kanavin
2023-04-12 16:18             ` talhacali
2023-04-12 16:19               ` talhacali

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=10320.1681297971251679769@lists.yoctoproject.org \
    --to=talhacali@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 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.