Upstream problem: Maintain a fork of zip

[NobodyXu]

According to the maintainer of zip @zamazan4ik :

The library is almost dead, so...

Also @zamazan4ik has no permission to publish a new version, so updates/bug fixes from zip is pretty slow.

Also, one of my PR which is intended to be used in cargo-binstall is also currently blocking as it requires reviewing from @Plecra but they don't have time/effort to review.

Honestly, I don't like forking upstream projects, but it seems that they are really in a bad shape. zip-rs/zip-old#232

[passcod]

I'm for it on the condition that these two (with tar) are forked under the name binstall-zip and binstall-tar and have an explicit mission of upstreaming changes (so no wild rewrites) and eventually disappearing (however that happens). Essentially we'll be keeping a patchset like distros sometimes do, not taking on the entire project.

[NobodyXu]

@passcod I agree with you on this.