Option to move zip-directory to "." (top level) of output zip file?

[jake1164]

All of my code is in a src/ folder so I have the zip-directory set to "src". The output of the mpy-zip is a src folder with the mpy files inside it, however, ideally I would love the src to be moved to the top folder ".".

[tekktrik]

Hi, sorry for the incredibly delayed response. So you're saying you want to run mpy-cross on the src/ folder but in the zip folder put that in the top level? Is that an example (or exactly) the use case you're describing?

[jake1164]

Hi, Yes that is the exact use case but probably should be slightly more generic incase people have the source in another sub folder.

[tekktrik]

If you want to compile the src/ folder but zip the top level, you should be able to set the zip directory to . (which is the default) and set the mpy directory to src/.  Please let me know if that helps or if I'm still misunderstanding!

[jake1164]

Ok, I will give this a try this weekend and see if that config work for my needs and let you know.

…

________________________________ From: Alec Delaney ***@***.***> Sent: Friday, December 29, 2023 1:43 PM To: adafruit/build-mpy ***@***.***> Cc: Jason Jackson ***@***.***>; Author ***@***.***> Subject: Re: [adafruit/build-mpy] Option to move zip-directory to "." (top level) of output zip file? (Issue #18) If you want to compile the src/ folder but zip the top level, you should be able to set the zip directory to . (which is the default) and set the mpy directory to src/. Please let me know if that helps or if I'm still misunderstanding! — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAN7MK553UVZUBCMTFPMNW3YL4FM3AVCNFSM6AAAAAA4NXUGMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGI3TCNRVGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tekktrik]

Hi, did that solve your issue?

[jake1164]

Hi, I have to confess that this dropped off my list this weekend, I will attempt to get to it one day after work this week.

…

________________________________ From: Alec Delaney ***@***.***> Sent: Monday, January 8, 2024 10:10 PM To: adafruit/build-mpy ***@***.***> Cc: Jason Jackson ***@***.***>; Author ***@***.***> Subject: Re: [adafruit/build-mpy] Option to move zip-directory to "." (top level) of output zip file? (Issue #18) Hi, did that solve your issue? — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAN7MK6IGHQ27KTHBTSU2DLYNSYMBAVCNFSM6AAAAAA4NXUGMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSGI4TSMBSGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jake1164]

Hi, I finally got around to this and now I remember.. when I do the "." for the zip-directory it has the whole content of my github repository, not just the converted mpy files. Which is sorta the opposite of what I am attempting to do. My Workflow name: Release CI on: release: types: [published] jobs: upload-mpy-zips: runs-on: ubuntu-latest steps: - name: checkout the current repo uses: ***@***.*** with: submodules: true - name: Create .version file run: echo '{ "version":"${{ github.event.release.tag_name }}" }' > src/.version - name: Run MPY Action uses: ***@***.*** with: github-token: ${{ secrets.GITHUB_TOKEN }} circuitpy-tag: "8.2.0" mpy-directory: "src" mpy-manifest-file: "mpy-manifest.txt" mpy-manifest-type: "exclude" zip-directory: "." zip-filename: "weather-matrix-${{ github.event.release.tag_name }}.zip" Resulting zip file. [cid:c1df4987-bacd-4ebc-b732-7482e087feef]

…

________________________________ From: Jason Jackson ***@***.***> Sent: Tuesday, January 9, 2024 6:22 AM To: adafruit/build-mpy ***@***.***>; adafruit/build-mpy ***@***.***> Cc: Author ***@***.***> Subject: Re: [adafruit/build-mpy] Option to move zip-directory to "." (top level) of output zip file? (Issue #18) Hi, I have to confess that this dropped off my list this weekend, I will attempt to get to it one day after work this week.

________________________________ From: Alec Delaney ***@***.***> Sent: Monday, January 8, 2024 10:10 PM To: adafruit/build-mpy ***@***.***> Cc: Jason Jackson ***@***.***>; Author ***@***.***> Subject: Re: [adafruit/build-mpy] Option to move zip-directory to "." (top level) of output zip file? (Issue #18) Hi, did that solve your issue? — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAN7MK6IGHQ27KTHBTSU2DLYNSYMBAVCNFSM6AAAAAA4NXUGMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSGI4TSMBSGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[tekktrik]

I'm still a little unclear of what the desired state you're looking for is. Would you mind creating a text or image diagram of the current and desired output of the tool?

I can however say that depending on what that is, it may be slightly out of scope. The goal of the action is to compile CircuitPython files and either zip them or a larger subset that includes them (i.e., zipping the compiled files or the entire project). if you want you're asking for is for the output to reflect a different filetree (or sub-filetree) than than repository, you may want to move things in the CI prior to running the actions using commands like mv.

But I may be misunderstanding your request, so please let me know if that isn't applicable to your request.

[jake1164]

Sure, I can look at this and send you something sometime in the next week or so.

…

________________________________ From: Alec Delaney ***@***.***> Sent: Tuesday, March 26, 2024 3:26 PM To: adafruit/build-mpy ***@***.***> Cc: Jason Jackson ***@***.***>; Author ***@***.***> Subject: Re: [adafruit/build-mpy] Option to move zip-directory to "." (top level) of output zip file? (Issue #18) I'm still a little unclear of what the desired state you're looking for is. Would you mind creating a text or image diagram of the current and desired output of the tool? I can however say that depending on what that is, it may be slightly out of scope. The goal of the action is to compile CircuitPython files and either zip them or a larger subset that includes them (i.e., zipping the compiled files or the entire project). if you want you're asking for is for the output to reflect a different filetree (or sub-filetree) than than repository, you may want to move things in the CI prior to running the actions using commands like mv. But I may be misunderstanding your request, so please let me know if that isn't applicable to your request. — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAN7MK2LOVB24VB4HI6YUC3Y2HDX7AVCNFSM6AAAAAA4NXUGMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGI4TQNRSGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>