-
Notifications
You must be signed in to change notification settings - Fork 48
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
Migrate to Tauri v2 #231
Comments
Well, it's already happening. v1 will not work on ubuntu 24 or debian testing because they have libwebkitgtk 4.1 while tauri v1 needs libwebkitgtk 4.0 |
Do you have some idea what sort of time frame we are looking at for having TrguiNG fully migrated to Tauri v2, or is that yet to be determined? |
I already started the migration, there is a branch on this repo https://github.com/openscopeproject/TrguiNG/tree/tauriv2 It works fine on windows, is semi-broken on linux with wayland and on macos reliably crashes. In the process of migration I filed multiple bugs for tauri and ran into issues I could not pinpoint. Unfortunately tauri v2 is not yet mature enough for production. But if you are on windows (or linux with x11) you can compile yourself. |
Ok, good to hear that it is work in progress :) Also, how would you rate the stability of TrguiNG Tauri v2 flavour on Linux X11? It sounds really strange to me that major distros are removing a Tauri V1 dependency if version 2 is still not ready for production, but I guess that sometimes, silly decisions are made :) |
The whole project is solo effort, except for some feature contributions here and there and arch AUR maintainer.
No issues as far as I could tell in fairly short testing.
Major distros don't care about any breakages that are outside of their ecosystem and almost no rust applications (tauri included) are in their ecosystem because rust update philosophy does not mesh with linux well. Arch is one exception. To give a rough timeframe, I expect tauri to have a bunch of bugfix releases in coming months and I will try again in 2-3 months. |
Ok, the I just might take TrguiNG on TauriV2 for a spin, since I am still on X11 :) And then my fingers are crossed that those bugs you encountered are fixed soon, allowing you to resume the migration effort. Will you be updating this thread with any progress, or maybe you are waiting with further info & announcements until the Tauriv2 version is fully ready for production ? |
Don't expect updates for couple months, I will post here and attach commits/labels when I resume work on this. |
Quick, and possibly stupid question: It just feels a bit silly to have this whole Gnome platform installed, when I'm otherwise on Plasma DE, but then I guess these things have nothing to do with each other and the Gnome stuff is merely needed because TrguiNG is built for Gnome, so to speak ? |
TrguiNG is not built for Gnome, flatpak version of it depends on it. What TrguiNG's upgrade to tauri v2 will do is enable native compilation on newer linux distros which don't have old dependencies that tauri v1 needs. That means you will be able to able to switch away from flatpak version of TrguiNG and use native version, then you will be able to get rid of gnome app platform (assuming you have no other flatpak apps depending on it). But if you continue to use flatpak TrguiNG then gnome platform will remain a dependency. |
Tauri v2 stable released recently, there is no immediate need to migrate but any future development and improvements to v1 are likely to stop, except for bugfixes.
Migrating is not trivial since a lot of code was reorganized.
https://v2.tauri.app/start/migrate/from-tauri-1/
The text was updated successfully, but these errors were encountered: