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
Then if I understood correctly, GIMP can only see the plug-in extensions in the set branch (i.e. only "2-40"). Right?
The problem
Apparently several people are complaining that they "lost" their plug-ins, but actually they have to manually reinstall them on the new branch. So they have to specifically reinstall org.gimp.GIMP.Plugin.GMic//2-40 for instance. That implies they have to understand the technicalities or the fact that we updated the runtime (the kind of details most people don't need to know).
Also this means the old org.gimp.GIMP.Plugin.GMic//2-3.36 is still there even if it is technically unusable (because the old GIMP using this branch is not anymore available since it was on the same stable branch). So we would slowly fill up space with outdated plug-ins too.
Solution
Is there currently a solution for these issues?
In other words: flatpak should recognize that the extension point version changed, hence check currently installed plug-ins, check if the same plug-in (same id) exist in the new branch and propose this new plug-in//branch package. Also it should propose to remove the old one as it became unreachable.
Did I understand all correctly? Is there a solution (i.e. we don't do it right, currently)? If not, shouldn't we make a report at flatpak and ask for this to work like proposed? Thanks. 🙂
The text was updated successfully, but these errors were encountered:
@hfiguiere From our discussions on #98 (comment), I got that:
Then if I understood correctly, GIMP can only see the plug-in extensions in the set branch (i.e. only "2-40"). Right?
The problem
Apparently several people are complaining that they "lost" their plug-ins, but actually they have to manually reinstall them on the new branch. So they have to specifically reinstall
org.gimp.GIMP.Plugin.GMic//2-40
for instance. That implies they have to understand the technicalities or the fact that we updated the runtime (the kind of details most people don't need to know).Also this means the old
org.gimp.GIMP.Plugin.GMic//2-3.36
is still there even if it is technically unusable (because the old GIMP using this branch is not anymore available since it was on the samestable
branch). So we would slowly fill up space with outdated plug-ins too.Solution
Is there currently a solution for these issues?
In other words:
flatpak
should recognize that the extension point version changed, hence check currently installed plug-ins, check if the same plug-in (sameid
) exist in the new branch and propose this newplug-in//branch
package. Also it should propose to remove the old one as it became unreachable.Did I understand all correctly? Is there a solution (i.e. we don't do it right, currently)? If not, shouldn't we make a report at flatpak and ask for this to work like proposed? Thanks. 🙂
The text was updated successfully, but these errors were encountered: