-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
thorium: Update to version 121.0.6167.204, fix autoupdate & checkver #12758
Conversation
Signed-off-by: Icey-Glitch <[email protected]>
Signed-off-by: Icey-Glitch <[email protected]>
/verify |
All changes look good. Wait for review from human collaborators. thorium
|
what is the status on this? |
Fixes #12832. |
I'm not sure if we should switch from AVX version (with which manifest was originally merged for version M117.0.5938.157) to SSE3. On the other hand, IMO, the "default" manifest should operate either the most capable version (which is AVX2) or the most compatible one (which is SSE3), the other modifications could be hosted in So I'm a bit stuck how to handle this situation properly. The same refers to Mercury browser (#12132, #12811) from the same author that has 4 release modifications (SSE3/SSE4/AVX/AVX2). |
I think the most reasonable way is to have the most compatible version be in extras. |
/verify |
All changes look good. Wait for review from human collaborators. thorium
|
Ok, since no other reactions, switched to SSE3 option and updated to the latest version (121.0.6167.204). |
Updates the manifest to support the new versioning in the thorium repo. Now looks for SSE3 version in the release to maintain support for older cpus as before, also adds architecture properties.