Dear list,
yesterday a guy on the general list reported me a bug and I did an update to one of my external, that is available on deken. Today I will update the deken repository; the suggested practice is update the external with incremented version or it's better to remove the old package? Moreover, there is a way to remove a package? I don't see a remove command...
Best regards,
Marco
On 2016-06-01 15:00, Marco Matteo Markidis wrote:
Dear list,
yesterday a guy on the general list reported me a bug and I did an update to one of my external, that is available on deken. Today I will update the deken repository; the suggested practice is update the external with incremented version or it's better to remove the old package?
whatever fits your workflow best.
personally, i think there is value in having older versions available, and deken tries it's best to sort newer versions before older versions (to gently nug the user into picking the newest available one, while still makig older versions available to them).
otoh, if your old package is completely broken or horribly buggy, there might be little use in keeping it around. (but then, somebody might rely on some buggy behaviour; or fixing the bug introduces a new bug; or...)
Moreover, there is a way to remove a package? I don't see a remove command...
open your browser, log in to https://puredata.info, navigate to your package and remove it.
dfamr IOhannes
Best regards,
Marco
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Thank you for your answer.
In these days I will update all the package.
Finally, I have a curiosity (don't have if it need a new thread): can I know how many downloads the package had from deken?
Best regards,
Marco
2016-06-02 9:01 GMT+02:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2016-06-01 15:00, Marco Matteo Markidis wrote:
Dear list,
yesterday a guy on the general list reported me a bug and I did an update to one of my external, that is available on deken. Today I will update the deken repository; the suggested practice is
update
the external with incremented version or it's better to remove the old package?
whatever fits your workflow best.
personally, i think there is value in having older versions available, and deken tries it's best to sort newer versions before older versions (to gently nug the user into picking the newest available one, while still makig older versions available to them).
otoh, if your old package is completely broken or horribly buggy, there might be little use in keeping it around. (but then, somebody might rely on some buggy behaviour; or fixing the bug introduces a new bug; or...)
Moreover, there is a way to remove a package? I don't see a remove command...
open your browser, log in to https://puredata.info, navigate to your package and remove it.
dfamr IOhannes
Best regards,
Marco
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
On 06/08/2016 05:11 PM, IOhannes m zmölnig wrote:
[...]¹
[...]
PS: [...]
the footnote was meant to refer to what ended up as a post scriptum. just in case somebody wondered.
oh: and feel free to request new features in the deken tracker, even if they are very low priority. somebody might just find the time to implement them.
gfmas IOhannes
-
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Marco Matteo Markidis