You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2024. It is now read-only.
I know #197 is about building godot, however I think this is better to separate out into it's own issue as it's a slightly different topic.
I'm looking into making a nix derivation (partly so I can learn nix moreso) of vpuppr just partly out of interest. As it requires a reproducible build, directly using your built godot binaries as your Readme suggests (https://github.com/virtual-puppet-project/godot-builds/releases/tag/latest) is not appropriate as if you update the latest release here it would break the reproducible build process (as it requires a sha256).
So I was wanting to confirm with you which build process of godot you believe to be most appropriate:
https://github.com/virtual-puppet-project/vpuppr/wiki/1.-Building-the-Godot-Fork states a process to build your custom godot, however doesn't specify which version/tag of godot to use and as such I believe some of the patches are failing. I understand it's v3 rather than v4, but which version specifically would be necessary.
I know #197 is about building godot, however I think this is better to separate out into it's own issue as it's a slightly different topic.
I'm looking into making a nix derivation (partly so I can learn nix moreso) of vpuppr just partly out of interest. As it requires a reproducible build, directly using your built godot binaries as your Readme suggests (https://github.com/virtual-puppet-project/godot-builds/releases/tag/latest) is not appropriate as if you update the latest release here it would break the reproducible build process (as it requires a sha256).
So I was wanting to confirm with you which build process of godot you believe to be most appropriate:
Thanks for your thoughts.
The text was updated successfully, but these errors were encountered: