Am 11.02.2025 um 17:22 schrieb Peter Kjellerstedt:
-----Original Message-----
From:bitbake-de...@lists.openembedded.org 
<bitbake-de...@lists.openembedded.org> On Behalf Of Stefan Herbrechtsmeier via 
lists.openembedded.org
Sent: den 11 februari 2025 16:00
To:openembedded-core@lists.openembedded.org
Cc: Stefan 
Herbrechtsmeier<stefan.herbrechtsme...@weidmueller.com>;bitbake-de...@lists.openembedded.org
Subject: [bitbake-devel] [RFC PATCH 10/30] conf: bitbake: add SRC_URI_FILES 
variable

From: Stefan Herbrechtsmeier<stefan.herbrechtsme...@weidmueller.com>

Add the variable SRC_URI_FILES to collect files whichs contains
additional SRC_URI lines.

Signed-off-by: Stefan Herbrechtsmeier<stefan.herbrechtsme...@weidmueller.com>
---

  meta/conf/bitbake.conf | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 8b607088c6..ed67500ba7 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -745,6 +745,7 @@ AUTOREV ="${@bb.fetch2.get_autorev(d)}"
  SRCPV = ""

  SRC_URI = ""
+SRC_URI_FILES = ""
Do we really need a new variable for this? Can't you add some parameter
instead to the URIs that should be handled separately?

The variable holds paths to files which contains dynamic generated SRC_URIs. The dynamic SRC_URIs are unknown at parse time and only the file paths are fix. The files are filled with generated SRC_URIs via a separate task.

If a parameter is not appropriate, then the name of the variable should
be reconsidered. Based on the name it is unclear what is expected to go
in SRC_URI and what should go in SRC_URI_FILES.

Would SRC_URI_MANIFESTS or SRC_URI_MANIFEST_FILES fit better?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#211213): 
https://lists.openembedded.org/g/openembedded-core/message/211213
Mute This Topic: https://lists.openembedded.org/mt/111125217/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to