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? 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, it becomes fetch specific and it places them alongside the fetch code, which it will need to remain tied to. I do feel we need to namespace them though as vendor is not specific enough to be directly in lib/oe. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#211187): https://lists.openembedded.org/g/openembedded-core/message/211187 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] -=-=-=-=-=-=-=-=-=-=-=-
