Hi, this probably is a dumb question and I am misunderstanding what this tool is supposed to do....
So I apologize in advance..
I was trying to use bita as a zsync replacement for AppImages.
For appimages, the .zsync information is embedded into the appimage, without breaking the appimage itself, and a .zsync file is also generated.
But bita, currently creates a compressed archive which breaks the appimage or any elf/binary file.
If .bita metadata could be embedded into original files, without breaking them (using a random section in the elf file or some other tricks), the use case of bita would be improved significantly.
Is such a feature in scope of your project? If not, no worries, this is still an amazing tool.
Thanks for making it FOSS
Hi, this probably is a dumb question and I am misunderstanding what this tool is supposed to do....
So I apologize in advance..
I was trying to use
bitaas a zsync replacement for AppImages.For appimages, the
.zsyncinformation is embedded into the appimage, without breaking the appimage itself, and a.zsyncfile is also generated.But
bita, currently creates a compressed archive which breaks the appimage or any elf/binary file.If
.bitametadata could be embedded into original files, without breaking them (using a random section in the elf file or some other tricks), the use case ofbitawould be improved significantly.Is such a feature in scope of your project? If not, no worries, this is still an amazing tool.
Thanks for making it FOSS