-
Notifications
You must be signed in to change notification settings - Fork 18
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
Use of -p option with the deploy command #8
Comments
Good point. We’ll see about making that change.
…-gary
On Jun 20, 2018, at 8:04 PM, cratcliff ***@***.***> wrote:
I am trying to use the pb_tool to package my plugin in an environment which is independent to the default QGIS user plugin folder so I can then test the installation/upgrade through the existing QGIS plugin manager.
I am currently using the following command pb_tool deploy –p c:\non-standard\my_qgisplugins to deploy to a folder which is NOT the default QGIS user plugin folder. What I am finding is that the plugin is being removed from the default QGIS user plugin folder (ie <home>.qgis2/python/plugins) and then deployed to the specified non-standard folder. It seems that when using the –p option, pb_tool is first checking for the existence of the plugin in the default QGIS user plugin folder, deleting it, then deploying to the specified path. Is this behaviour correct? I would have expected the existence check to be applied to the specified path and not the default QGIS user plugin folder when –p is used.
Also is possible to add a –p option to the zip command as well, which then passes the path to the deploy command when required prior to zipping?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#8>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAeKysfDiig55LSO2ZnG5_XCg7XEukm_ks5t-xs_gaJpZM4UxXYu>.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Gary Sherman
Founder, QGIS Project
-Open Source GIS Books:
*http://locatepress.com
-Geospatial Consulting & Hosting:
*http://geoapt.com
"We work virtually everywhere"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
|
g-sherman
added a commit
that referenced
this issue
Dec 26, 2018
g-sherman
added a commit
that referenced
this issue
Dec 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to use the pb_tool to package my plugin in an environment which is independent to the default QGIS user plugin folder so I can then test the installation/upgrade through the existing QGIS plugin manager.
I am currently using the following command
pb_tool deploy –p c:\non-standard\my_qgisplugins
to deploy to a folder which is NOT the default QGIS user plugin folder. What I am finding is that the plugin is being removed from the default QGIS user plugin folder (ie<home>.qgis2/python/plugins
) and then deployed to the specified non-standard folder. It seems that when using the–p
option, pb_tool is first checking for the existence of the plugin in the default QGIS user plugin folder, deleting it, then deploying to the specified path. Is this behaviour correct? I would have expected the existence check to be applied to the specified path and not the default QGIS user plugin folder when–p
is used.Also is possible to add a –p option to the zip command as well, which then passes the path to the deploy command when required prior to zipping?
The text was updated successfully, but these errors were encountered: