On Don, 2017-03-02 at 16:43 -0300, Alexandre Torres Porres wrote:
2017-03-01 19:07 GMT-03:00 zmoelnig@iem.at:
there is it will suggest to install there. if that folder does not exist (or is not writable), it will try ~/pd-externals. and so on.
so, the order deken searches seem to be: user-specific, global, application-specific
since the suer/global folders aren't created (anymore),
From what I remember, they have never been auto-created. And it wasn't an issue at all before Deken, since you either installed something through package manager, which creates all necessary directories, or you compiled something yourself and usually installed it with something like 'make install', which took care of the necessary directories, too.
Only since Deken exists, it's a question who or what creates those folders.
application is usually the first and only option. Now, in windows, that folder is not writeable... so deken cannot offer anything that'll work right away.
That's true. I thought that was unfortunate and I you agreed with me. I opened ticked [1] for Deken, so that Deken prompts you whether you want to install to the user specific folder and creates it on confirmation. IOhannes already went ahead and implemented it. :-)
I think that is quite an achievement (although the actual commit is pretty small). Thanks a lot, IOhannes.
But the thing is that it prompts you for downloading to this folder which is not writeable anyway... even though it will fail.
So I wonder and ask if it really skips an option if the folder is not writeable.
From what I understand, Deken prompts you only for directories where the user as write permissions for. If you gave yourself write privileges to the application specific or global search paths, yes, then Deken will ask to install there, if it doesn't find a user specific folder.