On Mon, Aug 15, 2022 at 10:54:06AM -0400, Marc Lavallée wrote: > Christopher Arndt sent a long and detailed answer, here's a shorter one.
One (metric) unit of Eternal Gratitude to both of you. So > pip install . will install to ~/.local/lib while > sudo pip install . will install to /usr/local/lib I find the destination directory depending on who the user pretends to be a bit strange, but it works ! Also tested this with a package that includes data files (*.npy) that should be found by the installed code, and also this works. The only minor problem is that the sudo version leaves two directories (build and *.egg-info) that can only be cleaned up by root. No problem on systems that allow sudo everything, but I may keep the Makefile just to offer 'sudo make clean', assuming most system will allow this. Unless there is a cleaner solution. Ciao -- FA _______________________________________________ Linux-audio-dev mailing list [email protected] https://lists.linuxaudio.org/listinfo/linux-audio-dev
