IOhannes wrote:
in declare-help it says: if you have zexy installed in the directory extra/zexy you can get it using [declare -stdpath extra/zexy].
i guess the example is not really tailored to zexy (it's just used as a placeholder)
a pity, it took me half a day to discover the problem was explicit with zexy and not with the other externals.
use [declare -stdpath zexy -stdlib zexy]
this works indeed, thanks.
(BTW deken gives a choice out of 2 zexy's, what's the difference?
mine gives me 9 zexy's and i can see the difference by reading them out loud.
i get 9 too, but 7 are greyed out. reading out loud the 2 left-overs (for Windows) brought me to the conclusion that one is for Vanilla and the other one for Pd-extended. correct me when i'm wrong.
rolf
On 05/09/2016 10:37 PM, rolfm@dds.nl wrote:
reading out loud the 2 left-overs (for Windows) brought me to the conclusion that one is for Vanilla and the other one for Pd-extended. correct me when i'm wrong.
almost :-) the one is stripped *from* Pd-extended (which already came with all known packages pre-installed), whereas the other has been packaged separately. the differing parts you are seeing in the package names are actually *version numbers* with "v0.0.extended" being a pseudo-version meaning "taken from the last Pd-extended release".
in sleepless nights, the deken devs tore apart Pd-extended binaries and bereaved it from all the libraries it included, created small dekenized libraries from them and uploaded. this is an attempt to make a lot of libraries available with deken from the beginning. the "lot" accumulates to 151 packages (that's a total of 85 different libraries), which is the reason why the poor devs didn't care to find out the *real* version number of each library.
gmadsr IOhannes
-
IOhannes m zmölnig -
rolfm＠dds.nl