Hello,
I was wondering if there's a proper way of removing/deleting packages from the puredata.info/Deken server. I uploaded our latest v0.3alpha1 Cyclone release using an older version of Deken from the Xenial repos, which apparently didn't upload using the directory structure of the newer Deken tool that creates subdirectories for library names and versions. I confirmed this by uploading a little test consisting of list abstractions I've been working on but hadn't really been planning on "officially releasing" yet using the newer Deken copied from the GitHub repo. After my little test, I deleted my test package via the puredata.info web interface but a day later it still appears in the Pd Deken library search tool, just with a dead link since it's no longer on the server (it was called pdklist). Since that doesn't seem like a proper way of removing libraries from Deken since whatever process Deken uses to know what libraries are on the server hasn't noticed the change, is there a proper way of doing this?
Eventually, I do plan on removing the cyclone builds from Deken and reuploading using the newer Deken tool. I couldn't find a way of moving alread uploaded files into folders via the pd.info web interface but perhaps that's a discussion for another time (but would also be a solution for my eventual goal). Thanks!
Derek
Derek Kwan www.derekxkwan.com
On 02/22/2017 09:14 PM, Derek Kwan wrote:
Hello,
I was wondering if there's a proper way of removing/deleting packages from the puredata.info/Deken server. I uploaded our latest v0.3alpha1 Cyclone release using an older version of Deken from the Xenial repos, which apparently didn't upload using the directory structure of the newer Deken tool that creates subdirectories for library names and versions. I confirmed this by uploading a little test consisting of list abstractions I've been working on but hadn't really been planning on "officially releasing" yet using the newer Deken copied from the GitHub repo. After my little test, I deleted my test package via the puredata.info web interface but a day later it still appears in the Pd Deken library search tool, just with a dead link since it's no longer on the server (it was called pdklist). Since that doesn't seem like a proper way of removing libraries from Deken since whatever process Deken uses to know what libraries are on the server hasn't noticed the change, is there a proper way of doing this?
a) this *is* the proper way to remove things. (there just seems to be a bug in the deken-server that it didn't update the search-results)
Eventually, I do plan on removing the cyclone builds from Deken and
b) i'm totally unconvinced that you should remove packages at all (apart from packages that you only uploaded in order to test deken). i think it is a disservice to your users to remove old versions of packages (even if they are outdated/buggy/...)
reuploading using the newer Deken tool. I couldn't find a way of moving alread uploaded files into folders via the pd.info web interface but perhaps that's a discussion for another time (but would also be a solution for my eventual goal). Thanks!
go to folder view ("contents"), select the files you want to move (via the checkboxes), click on the [Cut] button; navigate to the target folder and click the [Paste] button. if you only want to move a single file, the menu will offer a [cut] (and [paste]) option in the "Actions" dropdown.
gfasdrm IOhannes
2017-02-22 18:57 GMT-03:00 zmoelnig@iem.at:
Eventually, I do plan on removing the cyclone builds from Deken and
b) i'm totally unconvinced that you should remove packages at all (apart from packages that you only uploaded in order to test deken). i think it is a disservice to your users to remove old versions of packages (even if they are outdated/buggy/...)
agreed, but we're talking about a test version here, an experimental release, the idea is to replace it by a beta or final version. But I agree on the idea of keeping final releases there... otherwise, it'll populate the list too much
cheers
On Feb 22, zmoelnig@iem.at wrote:
a) this *is* the proper way to remove things. (there just seems to be a bug in the deken-server that it didn't update the search-results)
Looks like it's gone now as hoped.
b) i'm totally unconvinced that you should remove packages at all (apart from packages that you only uploaded in order to test deken). i think it is a disservice to your users to remove old versions of packages (even if they are outdated/buggy/...)
I am a bit wary of having millions of version of say, Cyclone, up on Deken, especially alpha versions, but I suppose that can be remedied by a more conservative approach to releasing/versioning so there SHOULDN'T be millions of alphas in the first place, which I suppose would be a sane approach to developing anyways. Anyways, I was just testing out Deken so I wanted it to go. I'll put it back up eventually once I do stuff like actual documentation...
go to folder view ("contents"), select the files you want to move (via the checkboxes), click on the [Cut] button; navigate to the target folder and click the [Paste] button. if you only want to move a single file, the menu will offer a [cut] (and [paste]) option in the "Actions" dropdown.
Thanks, managed to move Cyclone into proper subfolders and downloading from Deken still works.
Derek
2017-02-23 4:46 GMT-03:00 Derek Kwan derek.x.kwan@gmail.com:
managed to move Cyclone into proper subfolders and downloading from Deken still works.
what about the objects list? doesnt find cycle0.3 if i search for objects yet
On 2017-02-23 15:34, Alexandre Torres Porres wrote:
2017-02-23 4:46 GMT-03:00 Derek Kwan derek.x.kwan@gmail.com:
managed to move Cyclone into proper subfolders and downloading from Deken still works.
what about the objects list? doesnt find cycle0.3 if i search for objects yet
that's because the objects.txt file is broken. i wonder where you got the specs from.
the format is "objectname a 1-line description". seems like entries without the description get rejected.
mgfsdr IOhannes
2017-02-23 12:38 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
that's because the objects.txt file is broken. i wonder where you got the specs from.
I saw that the description wasn't used (at least 'yet') so I assumed they were optional
On 2017-02-23 16:54, Alexandre Torres Porres wrote:
2017-02-23 12:38 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
that's because the objects.txt file is broken. i wonder where you got the specs from.
I saw that the description wasn't used (at least 'yet') so I assumed they were optional
it's currently not used but it is mandatory.
fgasdrm IOhannes
guess i'll have to write the description of over 200 items in that list then :)
2017-02-23 13:08 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
On 2017-02-23 16:54, Alexandre Torres Porres wrote:
2017-02-23 12:38 GMT-03:00 IOhannes m zmoelnig zmoelnig@iem.at:
that's because the objects.txt file is broken. i wonder where you got the specs from.
I saw that the description wasn't used (at least 'yet') so I assumed they were optional
it's currently not used but it is mandatory.
fgasdrm IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
-
Alexandre Torres Porres -
Derek Kwan -
IOhannes m zmoelnig -
zmoelnig＠iem.at