user-settable install directory

[jmmmp]

My setup might be different from the normal user, I install Pd on a specific folder outside of my main drive - so that I can grab and copy my pd installation (windows). If deken would allow me to install the externals in another place, I could keep all my pd code in the same place.

Best,

jmmmp

[umlaeute]

👍

[umlaeute]

btw, this (and other things, like plugins for different backends) makes me wonder whether we should move the plugin into a separate directory deken-plugin (as in ~/pd-externals/deken-plugin/deken-plugin.tcl) so we can more easily deal with multiple-files.

[chr15m]

I am ok with moving the plugin into a subdirectory.

I don't want to require the user to download more than one tcl file. If we really need a more complex multiple-file architecture would prefer to have a Makefile that builds a single tcl distributable from all of the files.

On Debian a backend will be shipped, right?

I guess for me the most important thing is we get the puredata.info use-case working really well and do a release for users to get some solid testing. Maybe we can start integrating backends on a branch for the next release?

[umlaeute]

we could also use ~/.pd/deken.conf for storing a configuration file (what's the equivalent of that on OSX and W32?)

I just don't want to have it directly in ~/pd-externals/

[chr15m]

Ok, I see what you mean now. I was confused, sorry. I am find with putting it into ~/pd-externals/deken-plugin/deken-plugin.tcl and having a user config in there too.