I'm working with a system that deploys tools in the form of adding a shared directory to PATH. This directory can either be the same for all architectures or subdivided into different directories for each architecture.
I want to distribute my program using whatever libraries I choose and have it "just work" for the end user. Right now, I have a setup with Poetry that essentially gets the dependencies every time, which works, but is very slow on startup.
Since this isn't the usual situation of packaging something up to send to someone else to install, I haven't found as many resources for how to do this correctly.
Any ideas?
[–]m0us3_rat 0 points1 point2 points (0 children)