Crates.io incident report for 2020-02-20

Re:Crates.io incident report for 2020-02-20 by klysm on Saturday February 29, 2020 @01:53AM (#22449343)

I encourage you to look at the patch (it’s short). The callbacks are not between git2 and libgit2 so I think you are misunderstanding the nature of the problem.

I agree though that a pure rust implementation of libgit2 would be ideal.

[ Parent | on HN ]

Re:Crates.io incident report for 2020-02-20 by steveklabnik on Saturday February 29, 2020 @11:00AM (#22451174)

Some fun history: https://github.com/libgit2/libgit2/pull/3540

[ Parent | on HN ]

Re:Crates.io incident report for 2020-02-20 by klysm on Saturday February 29, 2020 @11:46AM (#22451446)

I was pleasantly surprised at how civil and thoughtful that conversation was! I was also expecting the “flame-retardant pants” to be necessary after reading the title.

I didn’t realize how complicated the backend tooling is to achieve the same portability as C - it seems so much simpler as a consumer of the toolchain. IIRC the bootstrapping problem is still something distros are fighting with today, but hopefully one day we can have rustc bundled with all the other standard build tools.

[ Parent | on HN ]