Am 11.02.2025 um 22:31 schrieb Richard Purdie:
On Tue, 2025-02-11 at 16:00 +0100, Stefan Herbrechtsmeier via
lists.openembedded.org wrote:
From: Stefan Herbrechtsmeier<stefan.herbrechtsme...@weidmueller.com>
Add a vendor package as base for package manager specific
implementations to resolve dependencies and populate vendor directories.
Add common dump and load function for SRC_URI files.
Signed-off-by: Stefan Herbrechtsmeier<stefan.herbrechtsme...@weidmueller.com>
---
meta/lib/oe/vendor/__init__.py | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 meta/lib/oe/vendor/__init__.py
Initially I was going to ask there to be a "fetch" or "download" in the
namespacing. That then made me wonder if in the interests of clarity
and namepacing, these vendor classes should go into
lib/bb/fetch2/vendor in bitbake?
The package isn't limited to fetch / download. In some cases it populate
the vendor directory and could be used for the license extraction in future.
I think it is a bad idea to move code into bitbake which isn't used by
bitbake. It will complicate future development without any benefit.
I appreciate the class in OE will use them and separation into bitbake
can be a bit awkward but it would mean we don't confuse this with any
other kind of vendoring
What do you mean by "any other kind of vendoring"?
, it becomes fetch specific and it places them
alongside the fetch code, which it will need to remain tied to.
It isn't fetch specific. The modules in the package parse lock files and
extract it content or populate the vendor directory.
I do feel we need to namespace them though as vendor is not specific
enough to be directly in lib/oe.
I chose vendor because it is the common name in the package manager to
create a folder which contains all package manager specific dependencies.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#211214):
https://lists.openembedded.org/g/openembedded-core/message/211214
Mute This Topic: https://lists.openembedded.org/mt/111123519/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
