From: Michael Ho <michael...@bmw.de> Hi,
The OpkgPM class has two arguments for advanced control over the ipk repository creation/use that I would like to make use of from outside of OpkgRootfs (which wraps OpkgPM). This is for purposes beyond just standard image generation so it's more of an advanced interface that is not intended for normal use. In this commit, I've added the variables IPKGREPO_TARGET and IPKGREPO_TARGET_PREPARED as interfaces to forward on to as ipk_repo_workdir and prepare_index when calling the OpkgPM constructor. Is this something that could be suitable for upstreaming or not likely? And if so, should I send a patch to document these variables or leave them undocumented like other IPKG variables (eg. IPKGCONF_TARGET). Thanks! Michael Ho (1): rootfs.py: expose prepared_index and ipk_repo_workdir for OpkgPM meta/lib/oe/package_manager/ipk/rootfs.py | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) -- 2.7.4
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#147684): https://lists.openembedded.org/g/openembedded-core/message/147684 Mute This Topic: https://lists.openembedded.org/mt/80401746/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
