Put on crates.io

[teburd]

would be nice to see this on crates.io

[danburkert]

I plan to, but right now it's blocked on retep998/winapi-rs publishing an updated crate (crates.io does not allow you to publish with non-crates.io dependencies).

[retep998]

You should no longer be blocked on that.

[BurntSushi]

@danburkert Is there anything I can do to help get this on crates.io?

[danburkert]

Hi all, sorry for the radio silence on this. I'm of the opinion that this project should be combined with rbranson/rust-mmap , and be pushed to crates.io as an update to that project. I'm attempting to reach out to the owner of that project via rbranson/rust-mmap#5, but there's no word back yet. If there's enough demand I may just go ahead and push under a different name. I'd also like to get a solution to #4 before pushing since that is almost certainly going to change the API.

[xrl]

@danburkert I've emailed @rbranson about this issue and haven't heard back. I think it's time to publish under another name? Is mmap-sys available?

This is holding me up from publishing my mmap-backed database lib.

[retep998]

Perhaps memmap or memorymap?

[jan-hudec]

I support @retep998's suggestions. https://crates.io/ does not have either.

[xrl]

The -sys suffix is the working convention for "system bindings". mmap-sys is open. You can view -sys packages here: https://crates.io/search?q=-sys . This library would follow that convention.

[retep998]

But this crate does not provide raw bindings to a specific system library. Rather it provides a high level wrapper around system stuff provided by other crates.

[xrl]

That's fair. I vote memorymap.

[danburkert]

The project has been renamed to memmap, and pushed to crates.io. Thanks all!