Re: [Qgis-developer] Updating core plugins
Thanks! 2013/5/29 Borys Jurgiel li...@borysjurgiel.pl: Dnia poniedziałek, 27 maja 2013 o 20:44:01 Victor Olaya napisał(a): Yes, non-core plugin overrides the core one (just because of the Python path order), so the only thing you can do is to make the core SEXTANTE version higher - at least QGIS will warn about the override and suggest manual uninstall. Borys, I think this is not working. I have received reports of people having SEXTANTE 1.0.9 interfering with the core 1.1 version, and I tested it myself. If you have a plugin in .qgis2, it will override the core one (as you mention), but no warning is produced. You're right, there is a bug. I'll fix it next week. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
Yes, non-core plugin overrides the core one (just because of the Python path order), so the only thing you can do is to make the core SEXTANTE version higher - at least QGIS will warn about the override and suggest manual uninstall. Borys, I think this is not working. I have received reports of people having SEXTANTE 1.0.9 interfering with the core 1.1 version, and I tested it myself. If you have a plugin in .qgis2, it will override the core one (as you mention), but no warning is produced. Thanks in advance Victor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
Dnia poniedziałek, 22 kwietnia 2013 o 12:49:11 Victor Olaya napisał(a): I didn't know about that qgis2 folder, but sounds like a good thing, and will solve the main problem that I was worried about. Once 2.0 is out, I can release new versions of SEXTANTE, and also release them when a new QGIS version is released, so people using a non-core version (a version that is not the one that comes with QGIS) can also update. Althought there is nothing wrong in the non-core plugins overriding the core ones, it's always cleaner and clearer if they are installed only when necessary. So personally I prefer to keep the non-core version number always a bit lower then the core one, so after QGIS upgrade the installer will rather warn and remove the obsolete update, instead of updating it with the recent update ;) It seems that you have been thinking about this already, so I guess that it will not be hard to keep a separate release schedule in case there are new features in SEXTANTE that would be good to publish without waiting for a new QGIS release. Exactly. It's what I called necessary in the paragraph above. Great work Borys! Seems that the early morning trips while at the Hackfest really worked out ;-) This behaviour is present for years. The only addition still to be made for 2.0 is removing the obsolete updates (now it only warns and suggests to do it manually). ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
I think decoupling the release of a new Sextante version from the release of a new QGIS release is very important. QGIS Master always has bugs that preclude the users from correctly testing Sextante. When Sextante was first released as a plugin, all users had to do was to checkout the svn repository to get the latest code. It was during this period that there was the highest number of people testing Sextante. Now, there are only a few. On Sun, Apr 21, 2013 at 10:24 PM, Victor Olaya vola...@gmail.com wrote: Hi all Having SEXTANTE as a core plugin in QGIS is really great, but I am worried about how that will affect users when 2.0 is released. My two main concerns are: - People currently using SEXTANTE as a non-core plugin will have 2 versions of SEXTANTE installed when they install 2.0. This is likely to cause strange behaviour, and, as some users have reported on the mailing list, it seems that the non-core plugin (in this case, the older version), will override the other one. Not a nice thing... The solution is to manually uninstall it, but that is going to cause a lot of confusion... - I have a few features that will not be ready for 2.0, but I would like to release them later, just releasing a new versino of SEXTATE independently. However, I think that core plugins cannot be updated. Installing the new one separately will cause two version to be installed... Any ideas on that? I see that the easiest solution would be to have something in the plugin manager that, in case of having two versions of a plugin, would use just the most recent one. Thanks in advance! Victor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
Dnia poniedziałek, 22 kwietnia 2013 o 07:18:02 Paolo Cavallini napisał(a): Il 22/04/2013 00:02, Borys Jurgiel ha scritto: Or uninstall the overriding plugin, if older. It would be probably more elegant solution... Or notify the user, and asking Do you want to remove the older version you installed previously?. All the best. Sure. No hidden uninstall without user's permit. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
I didn't know about that qgis2 folder, but sounds like a good thing, and will solve the main problem that I was worried about. Once 2.0 is out, I can release new versions of SEXTANTE, and also release them when a new QGIS version is released, so people using a non-core version (a version that is not the one that comes with QGIS) can also update. It seems that you have been thinking about this already, so I guess that it will not be hard to keep a separate release schedule in case there are new features in SEXTANTE that would be good to publish without waiting for a new QGIS release. Great work Borys! Seems that the early morning trips while at the Hackfest really worked out ;-) Cheers Victor 2013/4/22 Borys Jurgiel li...@borysjurgiel.pl: Dnia niedziela, 21 kwietnia 2013 o 23:24:49 Victor Olaya napisał(a): Hi all Having SEXTANTE as a core plugin in QGIS is really great, but I am worried about how that will affect users when 2.0 is released. My two main concerns are: - People currently using SEXTANTE as a non-core plugin will have 2 versions of SEXTANTE installed when they install 2.0. This is likely to cause strange behaviour, and, as some users have reported on the mailing list, it seems that the non-core plugin (in this case, the older version), will override the other one. Not a nice thing... The solution is to manually uninstall it, but that is going to cause a lot of confusion... Yes, non-core plugin overrides the core one (just because of the Python path order), so the only thing you can do is to make the core SEXTANTE version higher - at least QGIS will warn about the override and suggest manual uninstall. But we use the new .qgis2 directory, so I guess we just should tell users to not copy the .qgis to .qgis2 thoughtlessly... In addition, we could prevent QGIS 2.0 from loading uncompatible plugins. The repository and the installer assume, that plugins with qgisMinimumVersion==1.x are only compatible with 1.x unless it's strictly set by an optional tag qgisMaximumVersion (= 2.0). The same behaviour could be implemented for loading plugins. - I have a few features that will not be ready for 2.0, but I would like to release them later, just releasing a new versino of SEXTATE independently. However, I think that core plugins cannot be updated. Installing the new one separately will cause two version to be installed... Exactly, the base version in core and updates in user directory. The problem will be when you release a new version with QGIS 2.1, the updates for 2.0 will override the new version. But we can improve the override detection procedure for 2.1 (for example, the installer could uninstall the overriding version instead of only warning) Any ideas on that? I see that the easiest solution would be to have something in the plugin manager that, in case of having two versions of a plugin, would use just the most recent one. Or uninstall the overriding plugin, if older. It would be probably more elegant solution... Thanks in advance! Victor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Updating core plugins
Hi all Having SEXTANTE as a core plugin in QGIS is really great, but I am worried about how that will affect users when 2.0 is released. My two main concerns are: - People currently using SEXTANTE as a non-core plugin will have 2 versions of SEXTANTE installed when they install 2.0. This is likely to cause strange behaviour, and, as some users have reported on the mailing list, it seems that the non-core plugin (in this case, the older version), will override the other one. Not a nice thing... The solution is to manually uninstall it, but that is going to cause a lot of confusion... - I have a few features that will not be ready for 2.0, but I would like to release them later, just releasing a new versino of SEXTATE independently. However, I think that core plugins cannot be updated. Installing the new one separately will cause two version to be installed... Any ideas on that? I see that the easiest solution would be to have something in the plugin manager that, in case of having two versions of a plugin, would use just the most recent one. Thanks in advance! Victor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
Dnia niedziela, 21 kwietnia 2013 o 23:24:49 Victor Olaya napisał(a): Hi all Having SEXTANTE as a core plugin in QGIS is really great, but I am worried about how that will affect users when 2.0 is released. My two main concerns are: - People currently using SEXTANTE as a non-core plugin will have 2 versions of SEXTANTE installed when they install 2.0. This is likely to cause strange behaviour, and, as some users have reported on the mailing list, it seems that the non-core plugin (in this case, the older version), will override the other one. Not a nice thing... The solution is to manually uninstall it, but that is going to cause a lot of confusion... Yes, non-core plugin overrides the core one (just because of the Python path order), so the only thing you can do is to make the core SEXTANTE version higher - at least QGIS will warn about the override and suggest manual uninstall. But we use the new .qgis2 directory, so I guess we just should tell users to not copy the .qgis to .qgis2 thoughtlessly... In addition, we could prevent QGIS 2.0 from loading uncompatible plugins. The repository and the installer assume, that plugins with qgisMinimumVersion==1.x are only compatible with 1.x unless it's strictly set by an optional tag qgisMaximumVersion (= 2.0). The same behaviour could be implemented for loading plugins. - I have a few features that will not be ready for 2.0, but I would like to release them later, just releasing a new versino of SEXTATE independently. However, I think that core plugins cannot be updated. Installing the new one separately will cause two version to be installed... Exactly, the base version in core and updates in user directory. The problem will be when you release a new version with QGIS 2.1, the updates for 2.0 will override the new version. But we can improve the override detection procedure for 2.1 (for example, the installer could uninstall the overriding version instead of only warning) Any ideas on that? I see that the easiest solution would be to have something in the plugin manager that, in case of having two versions of a plugin, would use just the most recent one. Or uninstall the overriding plugin, if older. It would be probably more elegant solution... Thanks in advance! Victor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Updating core plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 22/04/2013 00:02, Borys Jurgiel ha scritto: Or uninstall the overriding plugin, if older. It would be probably more elegant solution... Or notify the user, and asking Do you want to remove the older version you installed previously?. All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlF0yAoACgkQ/NedwLUzIr7FTgCdHCG0gMGy/2+7ogar07KadEoT YyAAnizjXyG47bjvsfAg2ppow3e9wl1w =uTKs -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
