Replacing file initialized with LZ4 package causes I/O error

[Beuc]

It is possible to replace a file in the virtual filesystem when it was initialized using file_packager.py scripts.

However, when using its --lz4 option, replacing a file causes error:

# existing file:
> FS.writeFile('/renpy/common/DejaVuSans.txt', 'a')
Error: I/O error
# new file:
FS.writeFile('/renpy/common/new.txt', 'a')
undefined

[Beuc]

Browsing the sources, I see that LZ4 files are kept compressed (I thought they were decompressed once and for all when the file package is extracted) and then made read-only.
Would there be a way to convert LZ4 files to regular files when they are written over?
(I noticed I could unlink them prior to rewritting them, but that's not something my unzip library does.)

[kripken]

I think the idea with our LZ4 support is that you can have a huge amount of data in them, all kept compressed until you actually read it. So if you just read a small part, or read it incrementally, you can save a lot of memory.

[Beuc]

Yes that's what I understand too, but the read-only implementation breaks my use case where I have several layered filesets that may overwrite each others.

Being able to open(x, "w") LZ4 files for complete overwrite (without unlinking them first, with or without compression) would be nice.
Not high-priority though.

(In addition, maybe we can change the "I/O error" with a clearer read-only error or something.)

[kripken]

Agree on both that adding an option to write would be interesting, and a nicer error meanwhile would be good too.

[stale]

This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant.

[Beuc]

I believe the issue is still relevant :)

[stale]

This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant.