On Thu, 4 Jul 2019 21:47:44 +0800, you wrote: >yeah i agree .. my exp dealing with the tools highlights one tricky problem >we might face -> avoiding statically / bundled dependencies , while on the >same time getting all the tools to work .. most of them locks to specific >dependency version, and wont work on other.. and at the moment i'm not sure >whats the right approach to this, so really need input from others. My >current workflow is to install each tool and all their dependencies in >their own virtualenvs or vendor directory. Perhaps then the best solution is to document it, and then the SIG if created can do blog posts, videos, etc. to promote using Fedora using a documented procedure that works? _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
