panamax VS winsafe

We had previously tried panamax but it broke constantly. Well, recently we tried again and it worked beautifully this time and we used it to create an offline mirror. It was pretty straightforward to set up, has plenty of customization options, and is quick to update. It includes the Rust toolchain itself as well as the entire ecosystem of https://crates.io/. It's amazing, and it feels like we're online almost! The entire mirror is only about 150GB. Not bad!

I am trying to get a derivation for panamax, a mirror for crates.io, the package registry for Rust libraries.

It looks like panamax is also a program that can be used to mirror a local crates-io registry to ones device. And using .cargo/config one can point to it. https://github.com/panamax-rs/panamax

I’m looking for an equivalent of panamax for rust, for golang. Do you know if a tool like this exists ? The aim is to have a maximum of packages available (ideally all) in an offline environment.

We're no complete strangers to that ;-) (my handle on github is dureuill)

Finally got Panamax's (rust mirror) "serve" command to a point where I've finally made a PR for it!

Work on Panamax (a Rust mirror for rustup and crates.io). It's nearly complete, and as part of building a command to serve a downloaded mirror, I've implemented a warp proof of concept that serves a git repo: https://github.com/panamax-rs/warp-git

I know all that shit because I'm the author of Rust's WinSafe library, which is a safer Rust layer over native Win32, so I had to deal with a lot of shit like this.

[dependencies] winsafe = { git = "https://github.com/rodrigocfd/winsafe", features = ["kernel"] }

Externally, you can write a lot of native Windows stuff in Rust already. Personally, I'm having a lot of fun with WinSafe.

If you had such problems (which I also had in the past), I'm really interested in you opinion about WinSafe, and if it could help you solving them.

If you're after a native Windows application, WinSafe may suit your needs.

As the author of WinSafe, I can say it's tedious sometimes, but it's often very challenging, because you have to translate crazy unsafe behaviors into Rust's ownership model. It's surely hard, but also very rewarding at the end.

As the author of the WinSafe lib, I wholeheartedly agree.

I don't know how rare this is (or how rare it should be), but this issue warned me about this potential problem, and I had to make a huge refactoring to treat the possibility. I had to rethink many aspects of all handle implementations. It was hard work, but in the end it was worth it.

WinSafe says hello.

WinSafe, for example (which attemps to be a safe layer over the Windows API), provides lots of RAII automations. A fine example is the BeginPaint function: