the part that is missing from the docs is, that this file must be
uploaded besides the .dek file. so the objectlist-file is is *not* part
for the .dek file, but can be downloaded separately.
(so there's also little use in downloading deken packages and searching
their contents for the objectlist)

With my latest upload experiences, I found the *.dek.txt and the *.dek.sha256 are uploaded automatically with the *.dek file. It even attempts to create a GPG signing of the package and presumable upload that too. This was the Linux-deken, so YMMV.

i hope this helps,

gamsdr
IOhannes

Greetings,

Fred Jan

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list