-
Notifications
You must be signed in to change notification settings - Fork 393
memmap looks abandonned #359
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
Comments
A maintained mmap crate would be great, if you find one please let us know :| |
Should there be an advisory to tell people the crate is not maintained? Maybe it could also help to give it some publicity. |
We generally like for these sorts of advisories to steer people towards maintained alternatives if possible, however if none exist I guess that's ok too? |
It looks like this fellow has made a fork and is actually maintaining it to some degree. They've accepted some of the pull requests that are still waiting in the original repo. Although the issue tracker doesn't seem to be available on the github page. Did they disable that? Or is that just some odd side effect of a forked repo? |
I can't remember if it's the default behaviour of github to disable the issues page on forks, but either way there's an option in the project settings where the author should be able to re-enable it. |
There's a lot of weird issues with trying to use a fork of an old project as the new central repo for that project. If the original project is abandoned, it's probably best to create a new repo. That said, we can point to that repo in an advisory, if someone would like to make one. |
There's also https://github.com/RazrFalcon/memmap2-rs which seems to have reset the version number, but is also forked from the original. Should I suggest both as alternatives in the advisory? |
Sure, we try to be comprehensive when listing alternatives in unmaintained crate advisories |
I think this should have been closed by #501, right? |
Author never replied to danburkert/memmap-rs#90.
Was also mentioned in #173
I have no idea of an alternative. I hope there's one.
The text was updated successfully, but these errors were encountered: