Skip to content

Conversation

abstract-threadpool
Copy link

Per issue #3224 I have created a Ventoy-7zip repository which is a fork of the upstream 7zip mirror to create reproducible 7za.exe for 32-bit and 64-bit.

This upgrades to the newest 7-zip release (24.09).

The executables will not match exactly since we do not know the 7zip maintainers exact build configuration as they are not documented. Anyone can reproduce my build since it was produced by the GitHub workflow runner.

In the future when 7zip releases updates we can upgrade the Ventoy binaries easily:

  1. sync code changes and release tag to the upstream branch
  2. run GitHub workflow

This would work best if you owned the repository. You could either recreate this yourself or consider turning your project into a GitHub organization to manage the dependencies and/or the main repository. This could allow other to more easily help you.

@abstract-threadpool abstract-threadpool changed the title 7zip binary Remove 7zip BLOBs May 10, 2025
@phanirithvij
Copy link

phanirithvij commented May 25, 2025

Just a thought, your PR can add that github action to ventoy/ventoy repo itself. no need for an additional repo (even if owned by ventoy)

@DADA30000
Copy link

so, um, is this going to be merged/changed to be able to merge?

@kaliiiiiiiiii
Copy link

so, um, is this going to be merged/changed to be able to merge?

Probably not due to #3229 (comment)

I see no reason why the 7z build system should be owned by someone different than ventoy themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants