Hi list,
I’m currently trying to package up a set of externals for Deken release.
Following the docs here: https://github.com/pure-data/deken/blob/master/developer/README.md https://github.com/pure-data/deken/blob/master/developer/README.md Using version 0.6 of Deken on macOS 64-bit.
Based on the README, my expectation is that if I type:
$ deken package -v 1.0 foo
It will create a file: foo[v1.0](Darwin-x86_64-32).dek
However it actually creates: foo[v1.0].dek
Is this a Deken bug, or do I need to do something extra?
Thanks
Jamie
On 24.10.19 14:46, Jamie Bullock wrote:
Hi list,
I’m currently trying to package up a set of externals for Deken release.
Following the docs here: https://github.com/pure-data/deken/blob/master/developer/README.md https://github.com/pure-data/deken/blob/master/developer/README.md Using version 0.6 of Deken on macOS 64-bit.
Based on the README, my expectation is that if I type:
$ deken package -v 1.0 foo
It will create a file: foo[v1.0](Darwin-x86_64-32).dek
However it actually creates: foo[v1.0].dek
Is this a Deken bug, or do I need to do something extra?
maybe. could you please send the folder that you are trying to package up (probably via a pm), and the exact steps you are executing?
mgfasdr IOhannes