Thanks for sharing the ideas. https://discuss.tvm.ai/t/discuss-module-based-model-runtime-interface/5025 is the current proposed way for universal packaging, and that should resolve most of the current concerns.
While it is always possible to introduce another layer of abstraction for packaging, we also need to consider the minimum nature of the runtime and use as little abstraction as possible. i.e. the convention need to work on all platforms, languages and hopefully with as little dependency as possible (on ways to store libraries, availability of the dlopen etc). Our current conclusion in the other thread is to reuse the native executable and dll format and try to package things into the shared library(so that it will always be available and backend indepedent). Feel free to chime on on that thread for more thoughts --- [Visit Topic](https://discuss.tvm.ai/t/rfc-introduce-unique-module-in-tvm-for-uploading-all-deliverables-into-one/6567/2) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/091cc77367a436eb0fe8e817e9e13377d885348fb79a389850a7070f479357de).
