> For the complete documentation index, see [llms.txt](https://lwang010.gitbook.io/longw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lwang010.gitbook.io/longw/mlops/chap-4.-build-toolkit-for-team-or-yourself/tips/package-your-commonly-used-funcs-using-conda.md). # package your commonly used funcs using conda After the code is frozen, we can start with setting up a conda package and register it. Assume you already registered an account at anaconda, The minimal conda package requires: * the package name and version number * set up a meta.yml or (build.sh\&bld.bat) * use `conda build` to package it * login to anaconda and upload it to the repo The options to extend includes: * make the package work in all systems `(osx-64 linux-32 linux-64 win-32 win-64)`or multiple python version Steps for multiple platforms support: * use `conda convert tar.bz2 -p linux-64 -o output` * enter the output and upload the zipped file into the anaconda cloud * check updates at Issues I met: * If I am under the src, use `conda build .` directly. * conda build import test fails, but import works if test import is ignored in meta.yaml () References: * conda-build: {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://lwang010.gitbook.io/longw/mlops/chap-4.-build-toolkit-for-team-or-yourself/tips/package-your-commonly-used-funcs-using-conda.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.