On Wed, 19 Jul 2023 at 23:14, Charlie Johnston <[email protected]> wrote:
> I could see reusing the logic from the package_manager, but it would require
> changes to allow indices to be created for arbitrary directories (instead of
> being
> hardcoded based on package type), and adding some mechanism to
> create_packages_dir
> in the package_manager/__init__.py to handle feed creation tasks/feeds being
> dependent on other feeds.
>
> Are there limitations on changing the API of those classes and methods to add
> inputs? Alternatively, I could split the overlapping code into a helper method
> instead?
Thanks for the explanation!
The classes were written for the purpose of generating root
filesystems for images by constructing filtered package feeds in
images' ${WORKDIR}, but I think they should indeed be extended and
tweaked to allow generic feeds that can be then exported to
deploydirs. In particular create_packages_dir already does what is
needed for a filtered feed, and there really shouldn't be a second
implementation of that logic elsewhere.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184651):
https://lists.openembedded.org/g/openembedded-core/message/184651
Mute This Topic: https://lists.openembedded.org/mt/100243054/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-