Possibility of a Fruit Jam OS build in addtion to 9.x and 10.x

[FoamyGuy]

Right now when you download or build the dist zip the contents of the app are directly inside of CircuitPython10.x

I'm thinking it might be convenient to have a 3rd build inside of the dist zip alongside of 9.x and 10.x for Fruit Jam OS. In that build it would contain an intermediary folder like Fruit_Jam_Library/ and it would have the lib/ folder omitted. That folder would then be ready to copy/paste into CIRCUITPY/apps/ on a Fruit Jam running the OS.

Since the lib folder is omitted technically it could cause Import Error when run, but I think all or most of these libraries are included used by the OS itself so they should be there already. If there are some that are still missing there could be instructions for user to copy the necessary ones in to lib/ on their device.

The dist zip would look something like this:

[relic-se]

Thank you for bringing this up. The potential for libraries to be duplicated locally and taking up unnecessary space both for the library and downloaded applications is something that I am aware of and have mentioned here: #33.

In some ways, the packaging process for both 9.x and 10.x is completely unnecessary for the library as it is assumed that it is to be installed within FJOS. So, a better solution might be just to remove those copies altogether.

But what I think is a better question is how best to integrate this project within the Fruit Jam OS distribution. I have been holding off on the topic until this project matures, but it is getting close to that stage. Would you like to see this application moved directly into the main FJOS repository, kept in this repository and included as a submodule, kept in this repository and downloaded in during the build process (like the learn guide applications), etc?

[relic-se]

And on the topic of library management, this application requires an implementation of zipfile introduced here: https://github.com/relic-se/Fruit_Jam_Library/blob/main/zipfile.py. It may be best to move this over into a separate library rather than packaging it directly, but it needs some TLC and documentation before that can happen.

[FoamyGuy]

I wonder if it would be possible to use the core module zlib for handling the zipped files.

I'd be happy to see the Library included in the FJOS repo so that FJOS comes with it and allows people to download the projects from 3rd parties using it. Iirc there was preliminary discussion around it during the meeting once and other folks seemed receptive to that idea as well.

I will ask around internally to check if there is any warnings for third party downloads / code of conduct expectations that we need to add.

[relic-se]

I wonder if it would be possible to use the core module zlib for handling the zipped files.

The zipfile module does use zlib.decompress for decompressing .zip files. Out of the box, I doesn't have the ability to process a zipped archive internally. It can only handle raw streams of data. The module does the rest of the work of reading file directory trees, etc.

I'd be happy to see the Library included in the FJOS repo so that FJOS comes with it and allows people to download the projects from 3rd parties using it. Iirc there was preliminary discussion around it during the meeting once and other folks seemed receptive to that idea as well.

I will ask around internally to check if there is any warnings for third party downloads / code of conduct expectations that we need to add.

Awesome, this was my hope too. I really need to divert more time to polishing up the application. Then, I'll work to setting up a PR to include it. Any thoughts on my previous question on this? (see below reference)

Would you like to see this application moved directly into the main FJOS repository, kept in this repository and included as a submodule, kept in this repository and downloaded in during the build process (like the learn guide applications), etc?

[FoamyGuy]

I think I lean towards including it in the FJOS repo. That way additions to the library are done via PR to the FJOS repo.