Re: [PD] deken package question
On 06/08/2018 06:46 AM, Liam Goodacre wrote: > >> because the database is synched at least nightly. > > In that case, I would also suggest a console message that appears after deken > upload. Something like, "Your upload was successful. Please note that it can > take up to 24 hours before the package will appear for others to download in > the PD repository". please file a feature request in the github tracker. fmards IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
because the database is synched at least nightly. In that case, I would also suggest a console message that appears after deken upload. Something like, "Your upload was successful. Please note that it can take up to 24 hours before the package will appear for others to download in the PD repository". ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
On 06/07/2018 07:25 PM, Alexandre Torres Porres wrote: > it's weird, sometimes it takes about a day, no idea why > because the database is synched at least nightly. gfmards IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
it's weird, sometimes it takes about a day, no idea why 2018-06-07 13:40 GMT-03:00 Liam Goodacre : > So I followed your instructions and proceeded with the upload. The > packages are all sitting there in My Folder, but not appearing when I > search for them under Help --> Find Externals. It's been about 8 hours. Is > this normal, and if not, what could have gone wrong? > > https://puredata.info/Members/lgoodacre/software/context/4.0/ > > If you are looking for ideas for the command line utility, then maybe a > --recursive switch to the 'package' command to make it search in > sub-folders as well? > -- > *From:* Pd-list on behalf of IOhannes m > zmölnig > *Sent:* 03 June 2018 20:00 > *To:* pd-list@lists.iem.at > *Subject:* Re: [PD] deken package question > > On Sun, Jun 03, 2018 at 03:57:27AM +, Liam Goodacre wrote: > > I'm not asking for anything to be changed, just seeking advice on how > to make my upload without messing it up. > > but *I* am looking for a solution that makes the cmdline utility more > usable - > even if it requires changing things. > > > If I generate the package, delete the dummy external and the checksum, > then upload the package (generating a new checksum), will it work? > > i still don't understand what you mean by "delete the dummy external". > > probably something like the following: > > ~~~ > cp context/foo/bar.pd_linux context/ > deken package --version 0.1 context > zip -d context\[v0.1\]*.dek context/bar.pd_linux > rm context\[v0.1\]*.dek.* > deken upload context\[v0.1]*.dek > ~~~ > > the above *should* work (the principle; i haven't run any of the commands) > but heck, the worst thing that can happen if it doesn't > work is that you there has been some bogus upload to puredata.info, which > can > manually fix; or that there hasn't been an upload at all. > > fmgards > IOhannes > > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/ > listinfo/pd-list > > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/ > listinfo/pd-list > > ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
So I followed your instructions and proceeded with the upload. The packages are all sitting there in My Folder, but not appearing when I search for them under Help --> Find Externals. It's been about 8 hours. Is this normal, and if not, what could have gone wrong? https://puredata.info/Members/lgoodacre/software/context/4.0/ If you are looking for ideas for the command line utility, then maybe a --recursive switch to the 'package' command to make it search in sub-folders as well? From: Pd-list on behalf of IOhannes m zm?lnig Sent: 03 June 2018 20:00 To: pd-list@lists.iem.at Subject: Re: [PD] deken package question On Sun, Jun 03, 2018 at 03:57:27AM +, Liam Goodacre wrote: > I'm not asking for anything to be changed, just seeking advice on how to > make my upload without messing it up. but *I* am looking for a solution that makes the cmdline utility more usable - even if it requires changing things. > If I generate the package, delete the dummy external and the checksum, then > upload the package (generating a new checksum), will it work? i still don't understand what you mean by "delete the dummy external". probably something like the following: ~~~ cp context/foo/bar.pd_linux context/ deken package --version 0.1 context zip -d context\[v0.1\]*.dek context/bar.pd_linux rm context\[v0.1\]*.dek.* deken upload context\[v0.1]*.dek ~~~ the above *should* work (the principle; i haven't run any of the commands) but heck, the worst thing that can happen if it doesn't work is that you there has been some bogus upload to puredata.info, which can manually fix; or that there hasn't been an upload at all. fmgards IOhannes ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
On Sun, Jun 03, 2018 at 03:57:27AM +, Liam Goodacre wrote: > I'm not asking for anything to be changed, just seeking advice on how to > make my upload without messing it up. but *I* am looking for a solution that makes the cmdline utility more usable - even if it requires changing things. > If I generate the package, delete the dummy external and the checksum, then > upload the package (generating a new checksum), will it work? i still don't understand what you mean by "delete the dummy external". probably something like the following: ~~~ cp context/foo/bar.pd_linux context/ deken package --version 0.1 context zip -d context\[v0.1\]*.dek context/bar.pd_linux rm context\[v0.1\]*.dek.* deken upload context\[v0.1]*.dek ~~~ the above *should* work (the principle; i haven't run any of the commands) but heck, the worst thing that can happen if it doesn't work is that you there has been some bogus upload to puredata.info, which can manually fix; or that there hasn't been an upload at all. fmgards IOhannes ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
Hi IOhannes I'm not asking for anything to be changed, just seeking advice on how to make my upload without messing it up. If I generate the package, delete the dummy external and the checksum, then upload the package (generating a new checksum), will it work? From: Pd-list on behalf of IOhannes m zmölnig Sent: Saturday, June 2, 2018 10:41:43 PM To: pd-list@lists.iem.at Subject: Re: [PD] deken package question On Fri, Jun 01, 2018 at 02:40:33PM +, Liam Goodacre wrote: > I've got it to work, but when I generate the package it doesn't identify the > platform, giving me something like "context[v0.4]--.dek". I guessed that this > was because the externals I'm using are all in sub-folders, so I tried > copying one across to the main folder. Sure enough, the package now > identifies the platform correctly, but I'm not sure what the best course of > action is from here. Should I: the main obstacle here is that this is not really the common use-case for which deken cmdline is optimized (which is: packaging a single library, without internal dependencies). i think that the tool should cover the most common use cases, but there is no need to support edge cases (the difficulty is obviously in drawing the line). > 1. zip the package with the extra external, then delete it once the > compression is done (but this would probably invalidate the checksum?) well, if the checksum (and/or gpg signature) are missing and you are using `deken upload` for uploading they will be automatically (re)generated. (however, i was thinking about introducing "--gpg=no" and "--hash=no" args to prevent this (also for packaging). > 2. zip the package without the extra external, then rename it manually not sure i totally understand what you mean by this, but it sounds brittle. > 3. something else? probably a "--recursive" (or similar) flag to indicate that subdirectories should be searched recursively would help (please open a ticket in the issue tracker, if you agree). it was a conscious decision to *not* do recursive searches by default, i don't think i want to change that. mgfdsar IOhannes > > Thanks, > > Liam > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] deken package question
On Fri, Jun 01, 2018 at 02:40:33PM +, Liam Goodacre wrote: > I've got it to work, but when I generate the package it doesn't identify the > platform, giving me something like "context[v0.4]--.dek". I guessed that this > was because the externals I'm using are all in sub-folders, so I tried > copying one across to the main folder. Sure enough, the package now > identifies the platform correctly, but I'm not sure what the best course of > action is from here. Should I: the main obstacle here is that this is not really the common use-case for which deken cmdline is optimized (which is: packaging a single library, without internal dependencies). i think that the tool should cover the most common use cases, but there is no need to support edge cases (the difficulty is obviously in drawing the line). > 1. zip the package with the extra external, then delete it once the > compression is done (but this would probably invalidate the checksum?) well, if the checksum (and/or gpg signature) are missing and you are using `deken upload` for uploading they will be automatically (re)generated. (however, i was thinking about introducing "--gpg=no" and "--hash=no" args to prevent this (also for packaging). > 2. zip the package without the extra external, then rename it manually not sure i totally understand what you mean by this, but it sounds brittle. > 3. something else? probably a "--recursive" (or similar) flag to indicate that subdirectories should be searched recursively would help (please open a ticket in the issue tracker, if you agree). it was a conscious decision to *not* do recursive searches by default, i don't think i want to change that. mgfdsar IOhannes > > Thanks, > > Liam > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
