-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a table which shows supported formats && read / write support #14
Comments
After looking at libarchive, it looks like they list some supported formats: https://github.com/libarchive/libarchive/wiki/LibarchiveFormats . It looks like they might support zstd from looking at their issues but it's not listed in their formats :/ . |
Colin, I fear I won't survive to tell you. I'm in the process of dying of cancer and it looks like it's going to go right fast now, [email protected] will take over the digigal heritage and he well make the projekt open for adoptoion when time is due. So Sorry, especially for my 5yo son. |
That's absolutely terrible to hear. Can you create a permanently hosted page and maybe add a go fund me link for donations to your family? |
I looked at the go fund me page and there are loads of fundings running that your money would really make a difference in, so better leave it there. In my case the doctors still haven't invented a medicine that would give me some more years with my son, who just turned five years old this week. Hey, but medical miracles can always happen, maybe in the end it will all be good! As I said before, my true friend Wolfgang will take over the digital heritage, which mainly means finding a new maintainer for archivemount. My support for it was less than well anyway |
Stumbled here almost by chance. That is sad to read. |
I was curious if this would support zstd for reads. At the end of the readme it's stated that you support more formats for reading than writing. It might make an attractive readme to document supported formats in a table in the readme.
The text was updated successfully, but these errors were encountered: